From: Geoff Richards <qef@ungwe.org>
To: git@vger.kernel.org
Subject: Mistake in manpage for git-commit-tree?
Date: Sat, 14 Jul 2007 23:47:54 +0100 [thread overview]
Message-ID: <20070714224752.GD9011@ungwe.org> (raw)
Hi,
Just saw this in Documentation/git-commit-tree.txt at line 75:
A commit comment is read from stdin (max 999 chars). If a changelog
But from looking at the code it appears there is no such limit. That's
the size of the buffer used to read the commit message in, but it should
read multiple chunks of that size if you give it more than that.
If I'm not missing something, I'd suggest removing that bit in parens.
hth,
Geoff
next reply other threads:[~2007-07-14 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 22:47 Geoff Richards [this message]
2007-07-15 6:12 ` Mistake in manpage for git-commit-tree? 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=20070714224752.GD9011@ungwe.org \
--to=qef@ungwe.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