git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jakub Narebski" <jnareb@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] gitweb: Fixes and improvements related to diffs
Date: Wed, 26 Sep 2007 00:21:20 +0200	[thread overview]
Message-ID: <8fe92b430709251521j2b596016l186bdbb08c6cf816@mail.gmail.com> (raw)
In-Reply-To: <7vodfq4ch0.fsf@gitster.siamese.dyndns.org>

On 9/26/07, Junio C Hamano <gitster@pobox.com> wrote:
> "Jakub Narebski" <jnareb@gmail.com> writes:
>
> > This series of patches adds fixes, simplifications and improvements
> > related to diff handling in gitweb ('commit', 'commitdiff' views).
> >
> > Becaus I didn't have access to Internet, this series is based
> > on 1e61b7640d09015213dbcae3564fa27ac6a8c151 (v1.5.3.1-1-g1e61b76).
> > As I am sending it via GMail WWW interface, patches are send as
> > attachements.
> >
> > I send this series now, even without good Internet access,
> > because it contains two bugfixes, and one code fix. I'll try to
> > resend it rebase on top of current master later...
>
> I've parked the first two in 'master' and was hoping to roll
> them into 'maint'.  I haven't taken a look at the other three as
> I was waiting for a resend.  If you think some of them are
> bugfix material for 'maint', please mark them as such.

Third fixes a rare bug when gitweb screwed up names of files
in the patchset part of commitdiff view. This took place only
(diagnosed by pasky) when there were different files which
had the same preimage and the same postimage.

-- 
Jakub Narebski

      reply	other threads:[~2007-09-25 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 21:31 [PATCH 0/5] gitweb: Fixes and improvements related to diffs Jakub Narebski
2007-09-25 22:16 ` Junio C Hamano
2007-09-25 22:21   ` Jakub Narebski [this message]

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=8fe92b430709251521j2b596016l186bdbb08c6cf816@mail.gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).