From: Jeff King <peff@peff.net>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/2] Add a 'source' decorator for commits
Date: Tue, 28 Oct 2008 15:53:04 -0400 [thread overview]
Message-ID: <20081028195304.GC752@sigill.intra.peff.net> (raw)
In-Reply-To: <20081028194642.GB752@sigill.intra.peff.net>
On Tue, Oct 28, 2008 at 03:46:43PM -0400, Jeff King wrote:
>
> Hmm. Why a date-based hack to see what's on the topic branch? Why not
> just give an option to walk the graph twice, giving name-rev style
> annotations, and just let it be slow. People will mostly look at it by
> specifying just their topic branches anyway. IOW:
>
> git log ^origin/master my/topic1 my/topic2 my/topic3
And obviously you could split the "these are the commits to annotate"
specification from "these are the commits to show". But I actually think
in practice most users would want those to be the same.
-Peff
next prev parent reply other threads:[~2008-10-28 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 20:05 [PATCH 0/2] Random patches from my tree Linus Torvalds
2008-10-27 20:06 ` [PATCH 1/2] Add file delete/create info when we overflow rename_limit Linus Torvalds
2008-10-27 20:07 ` [PATCH 2/2] Add a 'source' decorator for commits Linus Torvalds
2008-10-28 5:45 ` Jeff King
2008-10-28 13:11 ` Pierre Habouzit
2008-10-28 13:19 ` Pierre Habouzit
2008-10-28 19:46 ` Jeff King
2008-10-28 19:53 ` Jeff King [this message]
2008-10-28 20:09 ` Pierre Habouzit
2008-10-28 20:27 ` Jeff King
2008-10-28 15:17 ` Linus Torvalds
2008-10-28 17:21 ` Linus Torvalds
2008-10-28 19:29 ` Jeff King
2008-10-27 20:37 ` [PATCH 0/2] Random patches from my tree 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=20081028195304.GC752@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--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).