Hi M. Ranganathan,
> To process SIP messages, SC relies on a stack called JAIN-SIP (API and
> reference implementation). However, the version used by SC is not a
> "vanilla" one and has a few modifications, for instance to replace the
> log4j by the standard Logger class.
Can you submit this change to jain sip ( assuming that the default can
be made to work as it does today ?)
I talked with Emil concerning the replacement of log4j in jain-sip and
IIRC he said that JAIN-SIP wasn't to take this direction (Emil, more
details about that?). Anyway, that would be better discussed on
> Currently, we provide no way to retrieve the exact sources of the
> version used in SIP Communicator. It is a problem from a free software
> point of view and also not very convenient for the developers.
That is a cvs problem. However, note that I do keep a date stamp on
the cvs repository.
Actually I think the problem is also on our side. We only store a
"JainSipRi1.2.jar" in our svn tree with no version information
whatsoever. That would be easily solved however. But that's true as well
that CVS sucks
> A first solution to solve that would be have a page on the wiki with the
> following informations:
> - current revision of JAIN-SIP used in our svn trunk
> - set of patches applied
> - possibly, a downloadable archive with the sources (patched or not)
> Additionally, I'd like to see that hosted in a version control system.
> It might be a bit heavy for our svn, but using an external git repo
> would really ease the work of rebasing our patches against the latest
> version of JAIN-SIP (you could be sure I'd propose that ;)). Here is a
> gitorious project to see how it would look like:
> What do you think?
Have you tried git-cvs and (I've only ever used git-svn). How do you
propose to keep the hosted git repository in sync with the master
(jain-sip.dev.java.net) cvs repository?
git-cvs is really feature poor compared to git-svn. It can be used to
import CVS commits in a git repo but I dont' think it's possible to
commit with it (whereas git makes also a great svn client), so you can't
get rid of your cvs working copy. Correct me if I wrong, I used it for
the first time today.
I see 2 cases where it would be useful to use git:
- to provide a read-only mirror that another party could use to
maintain its set of patches and have them rebased periodically. That
what I thought for SC as I have a hacky patch in mind that is not
commitable upstream (too SC specific, I'll think about it further to
find a cleaner solution).
- to do a full-migration to git.
Currently, here is what I do to update the gitorious repos:
(1) git cvsimport -v -k -p x -C jain-sip -r cvs -d:pserver:email@example.com:/cvs jain-sip
(2) git push gitorious refs/remotes/cvs/HEAD:refs/heads/cvs/HEAD
(1) will import/update the branches and tags from CVS in the following
places in my local repo:
... and so on
(2) will send the cvs head in the gitorious cvs/HEAD branch
On Wed, Jan 14, 2009 at 05:38:53PM -0500, M. Ranganathan wrote:
On Wed, Jan 14, 2009 at 5:12 PM, Sébastien Mazy <firstname.lastname@example.org> wrote:
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org