« Return to Thread: should we use bazaar?
Re: should we use bazaar?
by Robert Fischer
::
Rate this Message:
Interoperability with SVN is going to be hallmark requirement for DVCS moving forward -- it's
probably going to be the lingua franca of VCS. So as long as you keep SVN around, you can use
what's best now and shift to what's best in the future then, should you be so inclined.
~~ Robert.
Martin C. Martin wrote:
> Whatever's best now has little influence on what's best in 6 months or a
> year. If you're just looking to play around and find out what problems
> come up, you want to use the one that's best now. If you're looking at
> climbing a learning curve with DVCS, and really learning the ins and
> outs, you might want to choose based on a number of factors.
>
> Just my two cents,
> Martin
>
> Jason Dillon wrote:
>> This has been very interesting to follow, though I'm still a bit lost
>> as to which of these DVCS has the *best* support for working with an
>> existing SVN server to share branches. Seems like GIT should, but I
>> just installed the macport and there is no 'git-svn' commands, bzr
>> might be next, as it looks like the hgsvn stuff is still not very
>> mature (ie. can't commit back).
>>
>> Anyone know?
>>
>> --jason
>>
>>
>> On Jul 2, 2008, at 12:00 AM, Russel Winder wrote:
>>
>>> On Tue, 2008-07-01 at 18:38 +0200, Jochen Theodorou wrote:
>>>
>>>> I think it is a bit strange.. int the days of cvs you almost never had
>>>> free cvs server. cvsdude is the only one I know. Anyway, if this goes
>>>> through Codehaus for example, then the user of course still needs
>>>> access
>>>> to the server... I think I like the idea to use the mailing list to
>>>> handle patches and automatically merge after voting much better.
>>>
>>> In which case we could ask the Bazaar people whether the Codehaus people
>>> could run Patch Queue Manager and Bundle Buggy, assuming the Codehaus
>>> people are going to run Bazaar of course !
>>>
>>> Of course there is an assumption here of using Bazaar. I am not sure if
>>> Mercurial has anything equivalent. I suspect Git does not, but I am
>>> guessing.
>>>
>>> --
>>> Russel.
>>> ====================================================
>>> Dr Russel Winder Partner
>>>
>>> Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
>>> 41 Buckmaster Road, f: +44 8700 516 084
>>> London SW11 1EN, UK. m: +44 7770 465 077
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
probably going to be the lingua franca of VCS. So as long as you keep SVN around, you can use
what's best now and shift to what's best in the future then, should you be so inclined.
~~ Robert.
Martin C. Martin wrote:
> Whatever's best now has little influence on what's best in 6 months or a
> year. If you're just looking to play around and find out what problems
> come up, you want to use the one that's best now. If you're looking at
> climbing a learning curve with DVCS, and really learning the ins and
> outs, you might want to choose based on a number of factors.
>
> Just my two cents,
> Martin
>
> Jason Dillon wrote:
>> This has been very interesting to follow, though I'm still a bit lost
>> as to which of these DVCS has the *best* support for working with an
>> existing SVN server to share branches. Seems like GIT should, but I
>> just installed the macport and there is no 'git-svn' commands, bzr
>> might be next, as it looks like the hgsvn stuff is still not very
>> mature (ie. can't commit back).
>>
>> Anyone know?
>>
>> --jason
>>
>>
>> On Jul 2, 2008, at 12:00 AM, Russel Winder wrote:
>>
>>> On Tue, 2008-07-01 at 18:38 +0200, Jochen Theodorou wrote:
>>>
>>>> I think it is a bit strange.. int the days of cvs you almost never had
>>>> free cvs server. cvsdude is the only one I know. Anyway, if this goes
>>>> through Codehaus for example, then the user of course still needs
>>>> access
>>>> to the server... I think I like the idea to use the mailing list to
>>>> handle patches and automatically merge after voting much better.
>>>
>>> In which case we could ask the Bazaar people whether the Codehaus people
>>> could run Patch Queue Manager and Bundle Buggy, assuming the Codehaus
>>> people are going to run Bazaar of course !
>>>
>>> Of course there is an assumption here of using Bazaar. I am not sure if
>>> Mercurial has anything equivalent. I suspect Git does not, but I am
>>> guessing.
>>>
>>> --
>>> Russel.
>>> ====================================================
>>> Dr Russel Winder Partner
>>>
>>> Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
>>> 41 Buckmaster Road, f: +44 8700 516 084
>>> London SW11 1EN, UK. m: +44 7770 465 077
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: should we use bazaar?
| Free embeddable forum powered by Nabble | Forum Help |
