git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 16 Jul 2012 23:17:28 -0400	[thread overview]
Message-ID: <20120717031727.GA20945@sigill.intra.peff.net> (raw)
In-Reply-To: <7vipdn1qb7.fsf@alter.siamese.dyndns.org>

On Mon, Jul 16, 2012 at 12:03:40PM -0700, Junio C Hamano wrote:

> Jukka Lehtniemi <jukka.lehtniemi@gmail.com> writes:
> 
> > Display notes in the rev-list when switch '--notes' is used.
> > Also expand notes place holder (%N) in user format.
> > Previously rev-list ignored both of these.
> >
> > Signed-off-by: Jukka Lehtniemi <jukka.lehtniemi@gmail.com>
> > ---
> >
> > Thanks for your feedback Peff!
> 
> If it is an update for some old patch (I am guessing that is the
> case from "v2" and "feedback" above), please hint where the
> original can be found not to waste reviewers' time.

Agreed. For reference, v1 is here:

  http://thread.gmane.org/gmane.comp.version-control.git/193842

> As "git rev-list -h" does not say anything about "notes", I do not
> think this should be even called "Fix"; rather it is "teach rev-list
> to show notes with --notes", a new feature.

It does not, but "git rev-list --help" does (and it mentions "%N" for
the pretty userformat). So it's debatable whether it is a code bug or a
documentation bug. But whatever we call it, I think it is an
improvement.

> And as a new feature, "git rev-list -h" should be taught to include
> this new option in its output.  I didn't check the documentation but
> you may also want to add --notes there, too (hint: grep for "--pretty"
> to find where you may need to add the new option).

"rev-list -h" is already an unwieldy 35 lines, yet still manages to miss
many options (e.g., --grep, --author, --cherry-*, variations of
--left-right, --boundary, history simplification options like
--full-history, and so on). I don't think one more option is going to
break the camel's back, but I wonder if "rev-list -h" could use some
cleanup. E.g., maybe drop seldom used stuff like --bisect-vars, format
similar options on a single line to save space, and add in some missing
options.

My preference would actually be to just give up and refer people to the
manpage after a one or two line usage. But I think we have had that
discussion before and you did not agree.

-Peff

  reply	other threads:[~2012-07-17  3:17 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 [this message]
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

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=20120717031727.GA20945@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).