From: Jeff King <peff@peff.net>
To: Eric Blake <eblake@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] notes: mention --notes in more places
Date: Wed, 17 Oct 2012 01:51:37 -0400 [thread overview]
Message-ID: <20121017055136.GA12301@sigill.intra.peff.net> (raw)
In-Reply-To: <1350443975-19935-1-git-send-email-eblake@redhat.com>
On Tue, Oct 16, 2012 at 09:19:35PM -0600, Eric Blake wrote:
> Every so often, I search 'git send-email --help' to remember some
> option I've used in the past, only to discover that the option is
> documented instead in 'git format-patch --help'. Worse, even that
> command didn't document the option I was looking for today, which
> was how to include 'git notes' in the body of the commits I was
> mailing. Reading 'git notes --help' didn't mention this either,
> and I had to resort to searching the source code. It can't hurt
> to add some documentation to make this option less obscure.
I think this is a good direction, but...
> * git-notes.txt: Mention that --notes option exists in many
> commands to override defaults.
> * git-format-patch.txt: Include pretty-options, for things like
> --notes.
There are many things in pretty-options that would not be appropriate
for format-patch. We should probably wrap them like this:
diff --git a/Documentation/pretty-options.txt b/Documentation/pretty-options.txt
index 5e49942..a0f1d15 100644
--- a/Documentation/pretty-options.txt
+++ b/Documentation/pretty-options.txt
@@ -1,3 +1,4 @@
+ifndef::git-format-patch[]
--pretty[=<format>]::
--format=<format>::
@@ -27,6 +28,7 @@ people using 80-column terminals.
--oneline::
This is a shorthand for "--pretty=oneline --abbrev-commit"
used together.
+endif::git-format-patch[]
--encoding[=<encoding>]::
The commit objects record the encoding used for the log message
It may also make sense to show notes differently when outputting the
"email" format as format-patch does. E.g., using a triple-dash would
keep them separate from the commit message when using "git am". Like:
your commit message
Signed-off-by: You
---
your notes go here
We've talked about it several times, but it's never happened (probably
because most people don't actually use notes).
-Peff
next prev parent reply other threads:[~2012-10-17 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 3:19 [PATCH] notes: mention --notes in more places Eric Blake
2012-10-17 5:14 ` Junio C Hamano
2012-10-17 5:51 ` Jeff King [this message]
2012-10-17 6:25 ` Junio C Hamano
2012-10-17 13:30 ` Eric Blake
2012-10-17 19:05 ` Jeff King
2012-10-17 21:50 ` Junio C Hamano
2012-10-18 12:11 ` Michael J Gruber
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=20121017055136.GA12301@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.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).