From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 0/3] Documentation: Improve revision documentation
Date: Mon, 5 Jul 2010 17:26:06 +0000 [thread overview]
Message-ID: <AANLkTinEHbNFv-x1e4f6Jfi7sodNGSlKIPJMctFDSG7k@mail.gmail.com> (raw)
In-Reply-To: <cover.1278346173.git.git@drmicha.warpmail.net>
On Mon, Jul 5, 2010 at 16:11, Michael J Gruber <git@drmicha.warpmail.net> wrote:
> This mini-series sets up a new gitrevisions(7) man page so that people
> looking for revision syntax don't need to try to find it in
> git-rev-parse(1) which is cluttered with a lot of unrelated stuff (it's
> plumbing after all).
I like this series a lot. I often forget what our revision behavior is
and whether it's documented in git-rev-list, git-rev-parse or
something else. Then when I finally find it in git-rev-parse I have to
page down the manpage to discover it.
This is definitely something that should be standalone in
gitrevisions(7).
Acked-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
prev parent reply other threads:[~2010-07-05 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 16:11 [RFC/PATCH 0/3] Documentation: Improve revision documentation Michael J Gruber
2010-07-05 16:11 ` [RFC/PATCH 1/3] Documentation: split off rev doc into include file Michael J Gruber
2010-07-05 16:11 ` [RFC/PATCH 2/3] Documentation: gitrevisions Michael J Gruber
2010-07-14 6:16 ` Stephen Boyd
2010-07-14 8:42 ` Michael J Gruber
2010-07-14 16:49 ` Stephen Boyd
2010-07-05 16:11 ` [RFC/PATCH 3/3] Documentation: link to gitrevisions rather than git-rev-parse Michael J Gruber
2010-07-05 17:26 ` Ævar Arnfjörð Bjarmason [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=AANLkTinEHbNFv-x1e4f6Jfi7sodNGSlKIPJMctFDSG7k@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).