From: Nikolai Weibull <mailing-lists.git@rawuncut.elitemail.org>
To: git <git@vger.kernel.org>
Subject: [PATCH 0/3] Documentation additions and fixes
Date: Tue, 15 Nov 2005 00:20:01 +0100 [thread overview]
Message-ID: <11320104011696-git-send-email-mailing-lists.git@rawuncut.elitemail.org> (raw)
In-Reply-To:
While going over my Zsh-completion functions I found some options still
missing from the documentation. I also found some problems with some of
the documentation, so I fixed them as well.
nikolai
Documentation/git-checkout-index.txt | 10 +++++-----
Documentation/git-commit-tree.txt | 2 +-
Documentation/git-prune-packed.txt | 6 ++++++
Documentation/git-read-tree.txt | 4 ++++
Documentation/git-unpack-objects.txt | 6 +++++-
Documentation/git-update-index.txt | 2 +-
unpack-objects.c | 2 +-
7 files changed, 23 insertions(+), 9 deletions(-)
next reply other threads:[~2005-11-14 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 23:20 Nikolai Weibull [this message]
2005-11-14 23:20 ` [PATCH 1/3] Document the -n command-line option to git-unpack-objects Nikolai Weibull
2005-11-14 23:20 ` [PATCH 2/3] Document a couple of missing command-line options Nikolai Weibull
2005-11-14 23:20 ` [PATCH 3/3] Documentation nitpicking Nikolai Weibull
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=11320104011696-git-send-email-mailing-lists.git@rawuncut.elitemail.org \
--to=mailing-lists.git@rawuncut.elitemail.org \
--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