[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers-public] Re: Git commit notification hook

From: Sylvain Beucler
Subject: Re: [Savannah-hackers-public] Re: Git commit notification hook
Date: Mon, 25 Feb 2008 22:15:19 +0100
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

On Sat, Feb 23, 2008 at 08:13:34AM +0100, Jim Meyering wrote:
> > Is this your work/patch, or is it a different version?
> It's mine.
> I would have submitted it upstream, but when pushing
> multiple commits or tags, it's not useful:

Let's hope we can fix that (I didn't dig into this so I don't really
understand the issue yet) :)

Also, the dejagnu.git project got a curious problem: where essentially the commit
hook failed with "exit 1" (while I can't see where it could have done
that, given the error message).

I'm trying to reproduce this "push-update of tracking branch" error
message. Apparently it happens when the user pushes stuff in
refs/remotes/* . I can't see how user can affect this repository on
Savannah, because it's supposed to affect refs/heads/* instead.

dejagnu.git indeed has a refs/remote/origin/ directory _on Savannah_,
and it seems to mirror refs/heads/ . dejagnu.git also has a 'origin'
_branch_ (not remote). This is pretty confusing.

Do you have a clue on how dejagnu.git ended up in this state?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]