Hi Alexander, Sorry, I was away for a small while. Basically, its a copy (not a forked copy). This is due to several reasons, primarily to increase predictability in what we are using internally (all code needs gets tagged) and to guarantee availability of the repository due to any hiccups.
Medhavi On 2/10/07, Alexander Chemeris <[EMAIL PROTECTED]> wrote:
On 2/9/07, Medhavi Bhatia <[EMAIL PROTECTED]> wrote: > By mirroring I mean a meaningful local copy of the branch (in a different > repository). Right now if a copy is made, it cannot be tied to a tag or > snapshot, which means that updates on the main sipxTapi branch are harder to > track and bring back into the copy. It is really not a code stability issue, > but I was trying to see what folks on the list are doing if anyone is > maintaining a separate repository at all. Why do you want this? As I understand you want create fork of sipXtapi, am I right? -- Regards, Alexander Chemeris.
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
