What benefit is there to using git?
> -Original Message-
> From: Carl Trieloff [mailto:cctriel...@redhat.com]
> Sent: Monday, November 28, 2011 3:38 PM
> To: dev@qpid.apache.org
> Subject: GIT
>
>
> The ASF board is expanding the use of GIT, in the trial group for the
ASF. Do
> we want t
it is a lot easier to merge features, and work with others on changes.
Carl.
On 11/28/2011 04:19 PM, Steve Huston wrote:
> What benefit is there to using git?
>
>> -Original Message-
>> From: Carl Trieloff [mailto:cctriel...@redhat.com]
>> Sent: Monday, November 28, 2011 3:38 PM
>> To:
I would probably be quite happy just letting other projects play
guinea pig initially. I know a lot of the existing committers
(including me) already use git-svn and have done for years, which gets
you many of the benefits whilst letting those who need/want to use SVN
directly just keep doing so. N
Working with both, I've found "git pull" to be *much* faster than "svn
update". It's also much easier to specify which changed files you want
committed/posted. That said, they're both good. If you don't want the
full jump to Git perhaps Qpid can practice with Apache's Git Mirror
while still
As Robbie mentioned, most of the git fans are already using git-svn
(I'm one of them).
So we could perhaps wait for a bit to see how the trial unfolds.
My concern is, that not everybody may be ready to use git at this
point, so if we switch, then we will be disrupting the work for some
folks.
Rath
I have been using git for years now with Qpid, by cloning off the git
mirror and then use git-svn going foward (as per
http://wiki.apache.org/general/GitAtApache). I dont really do enough
updates to care much about the performance difference I must admit,
just the local branching and commits. I kno
After some more discussion, let's take a straw poll. I know many people
are using git already. If "many" accounts for most of our contributors,
we should really consider making the transition.
On Mon, 28 Nov 2011, Rajith Attapattu wrote:
As Robbie mentioned, most of the git fans are already
I would look closest at the ones that arent using it to see why they
cant or dont want to, and base the decision largely on that. For the
many already using it, do they care about the bits we dont currently
get through lack of direct git write access?
Robbie
On 28 November 2011 22:28, Justin Ross
Sorry, Rajith. Obviously, I agree!
On Mon, 28 Nov 2011, Justin Ross wrote:
After some more discussion, let's take a straw poll. I know many people are
using git already. If "many" accounts for most of our contributors, we
should really consider making the transition.
On Mon, 28 Nov 2011,
rather not move exclusively to git. However, if those that do a lot
more branching and changes strongly want to, I'll go along.
-Steve
> -Original Message-
> From: Carl Trieloff [mailto:cctriel...@redhat.com]
> Sent: Monday, November 28, 2011 4:40 PM
> To: Steve Huston
>
On Mon, Nov 28, 2011 at 05:28:27PM -0500, Justin Ross wrote:
> After some more discussion, let's take a straw poll. I know many
> people are using git already. If "many" accounts for most of our
> contributors, we should really consider making the transition.
+1
--
Darryl L. Pierce, Sr. Softw
On Mon, 2011-11-28 at 21:56 +, Robbie Gemmell wrote:
> I would probably be quite happy just letting other projects play
> guinea pig initially. I know a lot of the existing committers
> (including me) already use git-svn and have done for years, which gets
> you many of the benefits whilst lett
On 11/28/2011 05:38 PM, Robbie Gemmell wrote:
I would look closest at the ones that arent using it to see why they
cant or dont want to, and base the decision largely on that. For the
many already using it, do they care about the bits we dont currently
get through lack of direct git write access?
On 11/28/2011 05:28 PM, Justin Ross wrote:
After some more discussion, let's take a straw poll. I know many people are
using git already. If "many" accounts for most of our contributors, we should
really consider making the transition.
+1 for git
--
So, I'm not a git user, though I dare say I could learn... but I must admit
that I'd prefer not to be part of the pilot group and wait for others to
sort out any issues encountered before we consider moving across...
therefore I'd personally be -1 for moving in the trial... but ok for moving
at a l
A pilot has been done already, this is a wider group, so I would look at
it as do we want to be in the second wave of projects to GIT, or wait it
out.
from what I see infra has a solid handle on GIT from the projects that
have switched already
Carl.
On 11/30/2011 11:09 AM, Rob Godfrey wrote:
Is there any sort of info available on the implications of the move... e.g.
will we still easily be able to refer to the history for our current svn
repo?
-- Rob
On 30 November 2011 17:29, Carl Trieloff wrote:
>
>
>
> A pilot has been done already, this is a wider group, so I would look at
> it
On 11/30/2011 11:48 AM, Rob Godfrey wrote:
Is there any sort of info available on the implications of the move... e.g.
will we still easily be able to refer to the history for our current svn
repo?
All the history will carry over into git. Even personal git repo's have the full
history and IM
On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
> Is anyone using the git repo? I have tried both methods on the source page
> and I get the following errors:
>
> $ git clone git://jukka.zitting.name/qpid.git qpid
> Initialized empty Git repository in /var/data/build/tmp/qpid/.git/
> fatal: re
On Wed, Oct 21, 2009 at 4:30 PM, Aidan Skinner wrote:
> On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
>
>> Is anyone using the git repo? I have tried both methods on the source page
>> and I get the following errors:
>>
>> $ git clone git://jukka.zitting.name/qpid.git qpid
>> Initialized emp
perfect. thanks.
On Wed, Oct 21, 2009 at 10:32 AM, Aidan Skinner wrote:
> On Wed, Oct 21, 2009 at 4:30 PM, Aidan Skinner
> wrote:
> > On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
> >
> >> Is anyone using the git repo? I have tried both methods on the source
> page
> >> and I get the follo
21 matches
Mail list logo
