From: Jakub Narebski <jnareb@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Fix shortlog only showing HEAD revision.
Date: Wed, 03 Jan 2007 21:36:55 +0100 [thread overview]
Message-ID: <enh3v7$ji7$1@sea.gmane.org> (raw)
In-Reply-To: 20070103202555.GA25768@localhost
Robert Fitzsimons wrote:
> My change in 190d7fdcf325bb444fa806f09ebbb403a4ae4ee6 had a small bug
> found by Michael Krufky which caused the passed in hash value to be
> ignored, so shortlog would only show the HEAD revision.
>
> Signed-off-by: Robert Fitzsimons <robfitz@273k.net>
Identical change, better commit message (I think).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gitweb: Fix shortlog only showing HEAD revision.
Date: Wed, 03 Jan 2007 21:36:55 +0100 [thread overview]
Message-ID: <enh3v7$ji7$1@sea.gmane.org> (raw)
In-Reply-To: 20070103202555.GA25768@localhost
Robert Fitzsimons wrote:
> My change in 190d7fdcf325bb444fa806f09ebbb403a4ae4ee6 had a small bug
> found by Michael Krufky which caused the passed in hash value to be
> ignored, so shortlog would only show the HEAD revision.
>
> Signed-off-by: Robert Fitzsimons <robfitz@273k.net>
Identical change, better commit message (I think).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-03 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 19:21 GITWEB branch shortlog broken after recent update on kernel.org Michael Krufky
2007-01-03 20:25 ` [PATCH] gitweb: Fix shortlog only showing HEAD revision Robert Fitzsimons
2007-01-03 20:36 ` Jakub Narebski [this message]
2007-01-03 20:36 ` Jakub Narebski
2007-01-05 21:21 ` Michael Krufky
2007-01-05 21:25 ` J.H.
2007-01-03 20:30 ` [PATCH] gitweb: Make shortlog use 'h' (head) parameter again Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='enh3v7$ji7$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.