Le 21/05/2012 02:21, Hasan Diwan a écrit : Hi Hasan,
> Gents, > Maven does have git support[1]. So, it would be only a matter of updating > your poms to reflect the new scm type. -- H The fact tools like Maven supports Git is great. It is often more difficult to people, not tools... Well I switched from Subversion to Git about one year ago (after having switched from SCCS to RCS about 20 years ago, then from RCS to CVS, then from CVS to Subversion). There is a learning curve with Git, and it is not simple. However, you can get the first commands to do basic stuff in a few hours (checking things in and out, doing diffs), start to get used to it for a few days, and learn more stuff progressively (branches, multiple remote repository, stash ...). I would say it takes one or two months to be fluent. It is clearly worth the effort. > > On 20 May 2012 13:20, Christian Grobmeier <grobme...@gmail.com> wrote: > >> On Sun, May 20, 2012 at 12:43 AM, James Carman >> <ja...@carmanconsulting.com> wrote: >>> Perhaps classscan? :) >> >> makes perfect sense to me :-) Perfect for setting up something new, and also math for converting something existing as we seem to have volunteers. Luc >> >>> >>> On Sat, May 19, 2012 at 5:38 PM, Christian Grobmeier >>> <grobme...@gmail.com> wrote: >>>> On May 19, 2012 10:13 PM, "Gary Gregory" <garydgreg...@gmail.com> >> wrote: >>>>> >>>>> A one component test drive seems reasonable. >>>> >>>> +1 >>>> Not everybody is fluent with git. One component gives us the chance to >>>> document some best practices. >>>> >>>> Maybe it would be good to start with a sandbox comp. But i am afraid >> those >>>> are not active enough. >>>> >>>>> >>>>> Gary >>>>> >>>>> On May 19, 2012, at 4:08, Luc Maisonobe <luc.maison...@free.fr> wrote: >>>>> >>>>>> Le 16/05/2012 15:41, Jochen Wiedmann a écrit : >>>>>>> Well, with our multitude of projects, it might make sense to ask for >>>>>>> one or two of them >>>>>>> being migrated, so that we gather the experience. (I've got none so >>>>>>> far.) Would anyone >>>>>>> volunteer for the job of being involved? >>>>>> >>>>>> I was wondering if we should switch all components at the same time >> when >>>>>> everything is ready or as you propose switch one or two components >> early >>>>>> and use them as a template for other components. >>>>>> >>>>>> I am really interested in using Git access, as I already uses it for >>>>>> non-Apache projects and am really happy with it. In fact, for Apache >>>>>> projects I use git-svn. >>>>>> >>>>>> If we propose to switch one component first, I would be happy to >>>>>> volunteer for switching [math]. What do other developers think about >>>>>> Jochen idea ? >>>>>> >>>>>> Luc >>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Jochen >>>>>>> >>>>>>> >>>>>>> On Wed, May 16, 2012 at 9:52 AM, Christian Grobmeier >>>>>>> <grobme...@gmail.com> wrote: >>>>>>>> Its still in development. >>>>>>>> I have asked to switch to git with log4php before a few weeks and >> the >>>>>>>> answer was it is possible, if one of us gets involved in the >>>>>>>> git@apache project. I assume it is the the here. Its definitely >> not GA >>>>>>>> at the moment. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, May 16, 2012 at 9:39 AM, Jochen Wiedmann >>>>>>>> <jochen.wiedm...@gmail.com> wrote: >>>>>>>>> Completely OT: Is Git supported now? >>>>>>>>> >>>>>>>>> >>>> >> https://issues.apache.org/jira/browse/INFRA-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId276416#comment-13276416 >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
