From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>,
Frank Sorenson <frank@tuxrocks.com>,
git@vger.kernel.org
Subject: Re: How do I...
Date: Sat, 07 May 2005 09:58:35 +0100 [thread overview]
Message-ID: <1115456316.29495.57.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505061652240.2233@ppc970.osdl.org>
On Fri, 2005-05-06 at 16:54 -0700, Linus Torvalds wrote:
> But trying to be clever while building this up is just crazy talk. When
> diff-tree prints out the changes, it has no way of knowing what the
> context around it was - it doesn't know about merges far away, and it
> _shouldn't_ know.
Isn't that what I suggested? Start with full history, mark the
'interesting' commits which touch the file(s) in question, then prune.
--
dwmw2
next prev parent reply other threads:[~2005-05-07 8:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 9:49 How do I Frank Sorenson
2005-05-06 9:59 ` Thomas Glanzmann
2005-05-06 10:03 ` Thomas Glanzmann
2005-05-06 14:37 ` Dave Kleikamp
2005-05-06 16:39 ` Frank Sorenson
2005-05-06 17:58 ` Dave Kleikamp
2005-05-06 19:07 ` Frank Sorenson
2005-05-06 16:13 ` Linus Torvalds
2005-05-06 16:35 ` Junio C Hamano
2005-05-06 16:47 ` Frank Sorenson
2005-05-06 17:31 ` Daniel Barkalow
2005-05-06 18:56 ` Frank Sorenson
2005-05-06 17:09 ` Linus Torvalds
2005-05-06 18:39 ` David Woodhouse
2005-05-06 18:59 ` Linus Torvalds
2005-05-06 19:10 ` David Woodhouse
2005-05-06 22:57 ` Linus Torvalds
2005-05-06 23:20 ` David Woodhouse
2005-05-06 23:54 ` Linus Torvalds
2005-05-07 8:58 ` David Woodhouse [this message]
2005-05-06 19:35 ` Thomas Kolejka
2005-05-06 16:36 ` David Woodhouse
2005-05-07 0:45 ` Benjamin Herrenschmidt
2005-05-06 18:58 ` 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=1115456316.29495.57.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=frank@tuxrocks.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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).