From: Alexei Sholik <alcosholik@gmail.com>
To: git@vger.kernel.org
Cc: Alexei Sholik <alcosholik@gmail.com>
Subject: [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt
Date: Tue, 8 Mar 2011 15:16:08 +0200 [thread overview]
Message-ID: <1299590170-30799-1-git-send-email-alcosholik@gmail.com> (raw)
I was reading the man page on git-for-each-ref and noticed a few bugs and missing Authors and Documentation sections.
Sorry if I wasn't supposed to add them. I don't know if such editing should be done exclusively by the authors themselves or is it OK for others to do so. Just thought someone overlooked missing sections in the docs for this command.
Alexei Sholik (2):
Documentation: remove redundant colons in git-for-each-ref.txt
Add Author and Documentation sections to git-for-each-ref.txt
Documentation/git-for-each-ref.txt | 18 +++++++++++++++---
1 files changed, 15 insertions(+), 3 deletions(-)
--
1.7.2.3
next reply other threads:[~2011-03-08 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:16 Alexei Sholik [this message]
2011-03-08 13:16 ` [PATCH 1/2] Documentation: remove redundant colons in git-for-each-ref.txt Alexei Sholik
2011-03-09 7:55 ` Michael J Gruber
2011-03-08 13:16 ` [PATCH 2/2] Add Author and Documentation sections to git-for-each-ref.txt Alexei Sholik
2011-03-09 8:08 ` Michael J Gruber
2011-03-09 12:14 ` Alexei Sholik
2011-03-17 14:20 ` Will Palmer
2011-03-17 19:34 ` Jeff King
2011-03-17 19:51 ` Alexei Sholik
2011-03-17 19:54 ` Jeff King
2011-03-17 20:10 ` Alexei Sholik
2011-03-09 20:17 ` Junio C Hamano
2011-03-10 22:37 ` Jeff King
2011-03-10 23:09 ` Junio C Hamano
2011-03-11 6:20 ` Jeff King
2011-03-11 8:09 ` Junio C Hamano
2011-03-12 9:52 ` Alexei Sholik
2011-03-13 3:02 ` Jeff King
2011-03-13 6:34 ` Junio C Hamano
2011-03-13 6:47 ` Jeff King
2011-03-13 7:33 ` Junio C Hamano
2011-03-13 13:27 ` Michael J Gruber
2011-03-17 6:59 ` Jeff King
2011-03-09 19:54 ` [PATCH 0/2] A couple of tweaks in git-for-each-ref.txt Junio C Hamano
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=1299590170-30799-1-git-send-email-alcosholik@gmail.com \
--to=alcosholik@gmail.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).