E-mail notification from git post-receive hook -- commit diff is incorrect

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

E-mail notification from git post-receive hook -- commit diff is incorrect

Keith Marshall-3
Guys,

Do any of you pay any attention to our git commit notifications?  I know
I tend to only give them a fairly cursory inspection.  However, I have
noticed odd behaviour, following my last few mingw-get commits.

Basically: over the last two weeks, I've committed a series of changes
on the "gui-dev" branch.  On each occasion, the notification correctly
reports that branch "gui-dev" has been updated, and lists the hashes for
the commit sequence.  However, in each case, the following commit diff
bears no relation to these commits; rather it has persistently
reproduced the diff for my last (two week old) commit on "master".

Anyone care to follow this up, with a view to fixing it?

--
Regards,
Keith.

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|

Re: E-mail notification from git post-receive hook -- commit diff is incorrect

Earnie Boyd
On Thu, Oct 11, 2012 at 8:53 AM, Keith Marshall wrote:

> Guys,
>
> Do any of you pay any attention to our git commit notifications?  I know
> I tend to only give them a fairly cursory inspection.  However, I have
> noticed odd behaviour, following my last few mingw-get commits.
>
> Basically: over the last two weeks, I've committed a series of changes
> on the "gui-dev" branch.  On each occasion, the notification correctly
> reports that branch "gui-dev" has been updated, and lists the hashes for
> the commit sequence.  However, in each case, the following commit diff
> bears no relation to these commits; rather it has persistently
> reproduced the diff for my last (two week old) commit on "master".
>

I've noticed.

> Anyone care to follow this up, with a view to fixing it?

I'm using the SF supplied script to push it to the mail list.  I can
check to see if there is a newer version of the script from the source
master.

--
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr