Hi Jim, If your still feeling hesitant, how about we exclude the NMS bits from migrating to Git for now? Would that work for you?
On Thu, Jun 13, 2013 at 10:30 AM, Jim Gomes <[email protected]> wrote: > Of particular importance to how we do things, I found the following Q&A > extremely helpful. In particular, this answer ( > http://stackoverflow.com/a/4120179/444653) to the following question: > > http://stackoverflow.com/questions/4120001/what-is-the-git-equivalent-for-revision-number > > Our build process automatically generates build numbers by extracting > revision numbers. This would be an important feature in order to > potentially use git directly. > > > > On Fri, Jun 7, 2013 at 12:58 PM, Jim Gomes <[email protected]> wrote: > >> Hi Hiram, >> >> While that particular tool wouldn't quite work for us, I did a little more >> digging, and came across SubGit (http://subgit.com/). This tool looks >> like it potentially fill the gap seamlessly. I'll have to look further >> into it, but it does seem promising. >> >> I'll look into it, and revise my vote. >> >> Thanks, >> Jim >> >> >> >> On Fri, Jun 7, 2013 at 10:56 AM, Hiram Chirino <[email protected]>wrote: >> >>> Hi Jim, >>> >>> Git has a similar feature called submodules. See: >>> http://git-scm.com/book/en/Git-Tools-Submodules >>> >>> But honestly it should not be to much trouble to just script a few git >>> checkouts in your build process would it? >>> >>> I find SVN to be too slow for everyday use. Being able to be able to >>> fully use all the SCM features even when offline is also a very bonus. >>> >>> >>> >>> On Fri, Jun 7, 2013 at 1:36 PM, Jim Gomes <[email protected]> wrote: >>> > -1 >>> > >>> > We integrate the ActiveMQ NMS build tree into our build process using >>> > external references. Switching to Git will most likely make this >>> > impossible. If there is a solution that can continue to make this >>> seamless >>> > for us, then I could consider changing my vote. >>> > >>> > I would also ask what are the advantages? I see this as something that >>> > isn't broken and doesn't need fixing. Merging between branches with >>> SVN is >>> > extremely easy, and I do it all the time. I don't understand why others >>> > complain about it. The speed for checkouts, updates and commits is >>> > excellent. >>> > >>> > >>> > >>> > On Fri, Jun 7, 2013 at 5:25 AM, Willem jiang <[email protected]> >>> wrote: >>> > >>> >> +1 and it saves you lots of time if you need to merge between the >>> branches. >>> >> >>> >> >>> >> -- >>> >> Willem Jiang >>> >> >>> >> Red Hat, Inc. >>> >> FuseSource is now part of Red Hat >>> >> Web: http://www.fusesource.com | http://www.redhat.com >>> >> Blog: http://willemjiang.blogspot.com ( >>> http://willemjiang.blogspot.com/) >>> >> (English) >>> >> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) >>> >> Twitter: willemjiang >>> >> Weibo: 姜宁willem >>> >> >>> >> >>> >> >>> >> >>> >> On Friday, June 7, 2013 at 2:25 AM, Hiram Chirino wrote: >>> >> >>> >> > Seems some other projects at the ASF have been switching from SVN to >>> >> > Git. How you guys feel about making the switch too? I know >>> >> > personally I much prefer using Git to SVN and my main development >>> >> > model has been using SVN via Git. Just want to take a poll to see if >>> >> > any of the ActiveMQ developers would have strong objections to moving >>> >> > to Git. >>> >> > >>> >> > >>> >> > -- >>> >> > Hiram Chirino >>> >> > >>> >> > Engineering | Red Hat, Inc. >>> >> > >>> >> > [email protected] (mailto:[email protected]) | fusesource.com ( >>> >> http://fusesource.com) | redhat.com (http://redhat.com) >>> >> > >>> >> > skype: hiramchirino | twitter: @hiramchirino >>> >> > >>> >> > blog: Hiram Chirino's Bit Mojo >>> >> >>> >> >>> >> >>> >>> >>> >>> -- >>> Hiram Chirino >>> >>> Engineering | Red Hat, Inc. >>> >>> [email protected] | fusesource.com | redhat.com >>> >>> skype: hiramchirino | twitter: @hiramchirino >>> >>> blog: Hiram Chirino's Bit Mojo >>> >> >> -- Hiram Chirino Engineering | Red Hat, Inc. [email protected] | fusesource.com | redhat.com skype: hiramchirino | twitter: @hiramchirino blog: Hiram Chirino's Bit Mojo
