+1 same with Kevan

/Gurkan


________________________________
From: Kevan Miller <[email protected]>
To: [email protected]
Sent: Monday, January 19, 2009 11:06:44 PM
Subject: Re: additional usage of GIT for experimental features 


On Jan 16, 2009, at 5:42 PM, Mark Struberg wrote:

> Hi!
> 
> The Apache Infrastructure Team offers the possibility to mirror the SVN 
> archive to a GIT repo.
> 
> I just like to ask if anyone (besides me) is interested in using git for 
> sharing experimental features which are not elaborated enough for being 
> checked in to SVN?
> 
> If anyone has heard about git, but doesn't have a glue what's behind the 
> development model used with git then you should look at the following google 
> speech from Linus Torvalds:
> http://www.youtube.com/watch?v=4XpnKHJAok8
> 
> To state this clear: this is _not_ about using GIT instead of SVN, but only 
> _additionally_ to share immature features.

Hi Mark,
So, I confess that I'm not much of a GIT user. I know that there is growing 
interest in GIT within the ASF and that there are multiple ASF projects which 
are using GIT, in some form. I don't, however, know how these projects are 
using GIT.

I know that it's possible to use GIT in a private mode. Using GIT on their 
local machines, creating private branches, making local changes, etc, then 
committing their changes to SVN. I see absolutely no problem with this type of 
usage of GIT.

However, you are implying that we could use GIT as a means for sharing 
non-committed code among project members. I have some concerns about this. This 
could become a form of non-public communication among project members. Non-GIT 
users would not be able to participate in these "communications". This may be 
very GIT-like usage. However, it's potentially very un-ASF-like communication.

I don't know enough to evaluate the validity of my concerns without doing some 
more research. If you, or anyone else, know specifics about how other ASF 
projects are using GIT, that would be helpful...

--kevan 


      

Reply via email to