Re: [AVaRICE-user] Change of VCS

2011-11-21 Thread Joerg Wunsch
As Joerg Wunsch wrote: > Now that AVaRICE 2.11 has been shipped, I'd consider changing away > from CVS. ... > ..., I'd rather simply use Subversion which I'm > most used to. I finally did it. AVaRICE is using Subversion now! Please do no longer use the old CVS repository. (I disabled it in th

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Joerg Wunsch
As Seemanta Dutta wrote: > I would > stay away from centralized SCMs as much as possible. For what reasons, considering there's not going to be much traffic here, let alone, concurrent traffic. IOW, would you think of any other reasons than things like merge conflicts? -- cheers, J"org

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Weddington, Eric
> -Original Message- > From: Seemanta Dutta [mailto:seema...@gmail.com] > Sent: Monday, September 12, 2011 12:55 PM > To: AVaRICE list > Subject: Re: [AVaRICE-user] Change of VCS > > I have used mercurial before and find it quite smooth and logical. I would > st

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Seemanta Dutta
I have used mercurial before and find it quite smooth and logical. I would stay away from centralized SCMs as much as possible. //Seemanta On Mon, Sep 12, 2011 at 11:43 AM, Paul Klapperich < paul.klapper...@packetdigital.com> wrote: > On Mon, Sep 12, 2011 at 1:13 PM, Rick Mann wrote: > >> >> We

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Paul Klapperich
On Mon, Sep 12, 2011 at 1:13 PM, Rick Mann wrote: > > We use Subversion at Yahoo! and I've never heard of a commit being > corrupted. > Nobody here had either until I tried to use hg-svn, which builds the complete local history (as DVCSs like to have) by checking out each revision one after anot

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Rick Mann
Subversion. Just because it works pretty well, is widely used and "modern," and I'm used it. I wouldn't be opposed to Git, either. We use Subversion at Yahoo! and I've never heard of a commit being corrupted. -- Rick On Sep 12, 2011, at 6:48 , Joerg Wunsch wrote: > Now that AVaRICE 2.11 has b

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Joerg Wunsch
As Paul Klapperich wrote: > On the other hand, Subversion does have a long known random commit > corruption bug, which makes an old commit and a few after it > unusable. Interesting, thanks for the warning. I've never heard about (or experienced) that myself. > That might be > reason enough to

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Paul Klapperich
ing...@atmel.com> wrote: > > > > -Original Message- > > From: Joerg Wunsch [mailto:j...@uriah.heep.sax.de] > > Sent: Monday, September 12, 2011 7:48 AM > > To: AVaRICE list > > Subject: [AVaRICE-user] Change of VCS > > > > Now that AVaRICE 2.11 has been s

Re: [AVaRICE-user] Change of VCS

2011-09-12 Thread Weddington, Eric
> -Original Message- > From: Joerg Wunsch [mailto:j...@uriah.heep.sax.de] > Sent: Monday, September 12, 2011 7:48 AM > To: AVaRICE list > Subject: [AVaRICE-user] Change of VCS > > Now that AVaRICE 2.11 has been shipped, I'd consider changing away > from C

[AVaRICE-user] Change of VCS

2011-09-12 Thread Joerg Wunsch
Now that AVaRICE 2.11 has been shipped, I'd consider changing away from CVS. No, sorry, I'm not a big fan of Git (as it changes basically the entire user interface when comparing with CVS or Subversion). If at all, I'd consider Mercurial, though given that all the codebase is essentially a one-ma