git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Nick Edelen <sirnot@gmail.com>
Subject: Re: [PATCH 0/7 (v5)] rev-cache
Date: Tue, 06 Apr 2010 10:34:39 -0700	[thread overview]
Message-ID: <7vd3yciixc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <j2t6672d0161004060314j526e6d4q905bf427063b605f@mail.gmail.com> ("Björn Gustavsson"'s message of "Tue\, 6 Apr 2010 12\:14\:59 +0200")

In case people are wondering what the message Björn is responding to
said...

  From: Junio C Hamano <gitster@pobox.com>
  Subject: Re: [PATCH 0/7 (v5)] rev-cache
  Date: Mon, 05 Apr 2010 23:49:57 -0700
  References: <4BBA40B7.1060100@gmail.com>
  Message-ID: <7vaathjcru.fsf@alter.siamese.dyndns.org>

  Björn, I thought your "apply --whitespace=fix" patch was supposed to be
  able to cope with this series whose [2/7] introduces a new file with a
  trailing blank line "t/t6019-rev-cache-list.sh" (which is correctly fixed
  not to have that extra blank line at the end), and then a subsequent patch
  in the series [3/7] still tries to apply a patch assuming that the extra
  blank line was still there.

  But that is apparently not the case.  I think your series dealt only for
  the cases where the additional contents came _after_ the fixed-and-gone
  blank lines, and never dealt with the case where such lines appear in the
  context.

The message didn't go to vger because I botched while editing To/Cc lines.

      reply	other threads:[~2010-04-06 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 19:57 [PATCH 0/7 (v5)] rev-cache Nick Edelen
     [not found] ` <7vaathjcru.fsf@alter.siamese.dyndns.org>
2010-04-06 10:14   ` Björn Gustavsson
2010-04-06 17:34     ` Junio C Hamano [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=7vd3yciixc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sirnot@gmail.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).