From: Alexander C. <ale...@gm...> - 2011-10-22 07:24:39
|
Moving off-list is a bad idea is 99% of cases. People have more similar thoughts and problems then it may seem :) Ok, I see the point. But why not to continue maintain OpenBTS-UHD in git? I see no reason to maintain an svn repository for this. I don't see any developers here who hate git except David, and for users it just doesn't matter. I think everyone where happy when OpenBTS-IHD was on github, it's very convenient. PS I should admit, I personally like Mercurial more then git, but I work with git as well and don't have pet peeve for it. On Sat, Oct 22, 2011 at 11:15, Kurtis Heimerl <khe...@cs...> wrote: > Thomas and I moved this off-list, but your response was EXACTLY the > same as mine, so I suppose that may have been a mistake. > > I'll try to paraphrase Thomas: The short hand is that a second repo > allows users to have a repo with stuff not covered (or not yet > covered) by the CLA. > > I think that's a fair point, but not one I'd personally support. I'm > mostly inclined to make sure that the repo setup encourages us all > sharing (and working on) the same code base, CLA or not. > > On Fri, Oct 21, 2011 at 11:57 PM, Alexander Chemeris > <ale...@gm...> wrote: >> But why do you need a second svn repo? I used svn a lot and never had a need >> for a second repo. I'm quite surprised. >> >> -- >> Alexander Chemeris >> Sent from my Android device. Sorry for my brevity. >> >> On Oct 22, 2011 4:55 AM, "Thomas Tsou" <tt...@vt...> wrote: >> >> On Fri, Oct 21, 2011 at 5:35 PM, Kurtis Heimerl >> <khe...@cs...> wrote: >>> You can't push a... >> >> No, you can definitely do that. >> >> You can't easily go from one svn repo to a git repo and then to >> another, different svn repo. Actually, you can't simply go from one >> svn repo to another svn repo to begin with. That's just the nature of >> centralized version control; you're only supposed to have one main >> repo that everyone uses. >> >> Thomas >> > -- Regards, Alexander Chemeris. |