git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Subject: [RFC/PATCH 0/3] Documentation: Improve revision documentation
Date: Mon,  5 Jul 2010 18:11:38 +0200	[thread overview]
Message-ID: <cover.1278346173.git.git@drmicha.warpmail.net> (raw)

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).

If that concepts is OK, I actually suggest changing the actual content a
bit. Also, I found a copule of typos around the areas which I touched
but saved this for an extension of this series.

Michael J Gruber (3):
  Documentation: split off rev doc into include file
  Documentation: gitrevisions
  Documentation: link to gitrevisions rather than git-rev-parse

 Documentation/Makefile                 |    2 +-
 Documentation/git-cat-file.txt         |    2 +-
 Documentation/git-check-ref-format.txt |    2 +-
 Documentation/git-cherry-pick.txt      |    4 +-
 Documentation/git-diff.txt             |    4 +-
 Documentation/git-fast-import.txt      |    2 +-
 Documentation/git-format-patch.txt     |    2 +-
 Documentation/git-log.txt              |    3 +-
 Documentation/git-push.txt             |    2 +-
 Documentation/git-reflog.txt           |    2 +-
 Documentation/git-rev-parse.txt        |  200 +-------------------------------
 Documentation/git-revert.txt           |    2 +-
 Documentation/git-show-branch.txt      |    2 +-
 Documentation/git-show.txt             |    2 +-
 Documentation/git.txt                  |    2 +-
 Documentation/gitcore-tutorial.txt     |    2 +-
 Documentation/gitk.txt                 |    2 +-
 Documentation/gitrevisions.txt         |   35 ++++++
 Documentation/revisions.txt            |  199 +++++++++++++++++++++++++++++++
 Documentation/user-manual.txt          |    8 +-
 20 files changed, 257 insertions(+), 222 deletions(-)
 create mode 100644 Documentation/gitrevisions.txt
 create mode 100644 Documentation/revisions.txt

             reply	other threads:[~2010-07-05 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 16:11 Michael J Gruber [this message]
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 ` [RFC/PATCH 0/3] Documentation: Improve revision documentation Ævar Arnfjörð Bjarmason

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=cover.1278346173.git.git@drmicha.warpmail.net \
    --to=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).