From: "David Tweed" <david.tweed@gmail.com>
To: "Johannes Sixt" <johannes.sixt@telecom.at>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH/RFC] Revert "filter-branch: subdirectory filter needs --full-history"
Date: Tue, 27 May 2008 11:55:46 +0100 [thread overview]
Message-ID: <e1dab3980805270355n6121ee9ehc285497b20b70a15@mail.gmail.com> (raw)
In-Reply-To: <200805262109.19015.johannes.sixt@telecom.at>
On Mon, May 26, 2008 at 8:09 PM, Johannes Sixt <johannes.sixt@telecom.at> wrote:
> This reverts commit cfabd6eee1745cfec58cfcb794ce8847e43b888a. I had
FWIW, applying this patch (getting 1.5.6.rc0.29.g3beb5.dirty) it now
filters the case I was trying successfully (although I understand
Johannes' point that this fix only works because my commit graph is
only "quite messy" and it wouldn't work if it was "extremely messy":-)
).
Thanks to Johannes for his time looking at this.
--
cheers, dave tweed__________________________
david.tweed@gmail.com
Rm 124, School of Systems Engineering, University of Reading.
"while having code so boring anyone can maintain it, use Python." --
attempted insult seen on slashdot
next prev parent reply other threads:[~2008-05-27 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e1dab3980805230808s59798351r9ed702c7d0dedd2a@mail.gmail.com>
2008-05-24 20:16 ` rev-list --parents --full-history + path: something's fishy Johannes Sixt
2008-05-25 1:21 ` Linus Torvalds
2008-05-25 12:26 ` Johannes Sixt
2008-05-25 21:23 ` Linus Torvalds
2008-05-26 19:09 ` [PATCH/RFC] Revert "filter-branch: subdirectory filter needs --full-history" Johannes Sixt
2008-05-27 10:55 ` David Tweed [this message]
2008-05-28 5:25 ` Junio C Hamano
2008-05-25 19:58 ` rev-list --parents --full-history + path: something's fishy Johannes Sixt
2008-05-25 21:30 ` Linus Torvalds
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=e1dab3980805270355n6121ee9ehc285497b20b70a15@mail.gmail.com \
--to=david.tweed@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
--cc=torvalds@linux-foundation.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 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).