From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jukka Lehtniemi <jukka.lehtniemi@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] Fix notes handling in rev-list
Date: Thu, 19 Jul 2012 13:25:50 -0400 [thread overview]
Message-ID: <20120719172550.GA12883@sigill.intra.peff.net> (raw)
In-Reply-To: <7vr4s7vfal.fsf@alter.siamese.dyndns.org>
On Thu, Jul 19, 2012 at 10:20:18AM -0700, Junio C Hamano wrote:
> > So for plumbing, I think this is the wrong direction, anyway. The real
> > value of this patch is that the pretty-printed code path would work more
> > like git-log (especially the "%N" format, which lets callers make their
> > own micro-format for specifying all the bits they are interested in).
>
> Yeah, but at that point the obvious question becomes "why you aren't
> using 'git log' in the first place".
I dunno. I guess there are other plumbing-like behaviors of rev-list
that you would want, but the only ones I can think of are diff options,
which rev-list does not handle at all.
> > Maybe the best thing is to simply disallow --notes when not using a
> > pretty-printed format.
>
> Yeah, or simply ignore it.
I'd rather generate an error to make it more obvious what is happening
(and it is not that we are somehow failing to find any notes). And it
might help prevent the later question of: why does "git rev-list
--oneline --notes" show notes, but "git rev-list --notes" silently
ignores it?
-Peff
prev parent reply other threads:[~2012-07-19 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 19:38 [PATCH] rev-list: fix place holder %N (notes) in user format Jukka Lehtniemi
2012-03-25 0:55 ` Jeff King
2012-07-16 18:30 ` [PATCH v2] Fix notes handling in rev-list Jukka Lehtniemi
2012-07-16 19:03 ` Junio C Hamano
2012-07-17 3:17 ` Jeff King
2012-07-17 3:40 ` Junio C Hamano
2012-07-17 3:51 ` Jeff King
2012-07-17 3:46 ` Jeff King
2012-07-17 5:42 ` Junio C Hamano
2012-07-17 21:22 ` Jukka Lehtniemi
2012-07-18 7:21 ` Jeff King
2012-07-18 22:39 ` Junio C Hamano
2012-07-19 11:35 ` Jeff King
2012-07-19 17:20 ` Junio C Hamano
2012-07-19 17:25 ` Jeff King [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=20120719172550.GA12883@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jukka.lehtniemi@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).