From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Automatically line wrap long commit messages.
Date: Tue, 30 May 2006 01:38:46 -0700 [thread overview]
Message-ID: <7vhd373o15.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060529094605.GB27194@spearce.org> (Shawn Pearce's message of "Mon, 29 May 2006 05:46:05 -0400")
Shawn Pearce <spearce@spearce.org> writes:
> OK. Ignore both patches then. Two negative votes in such a short
> time suggests they are probably not generally accepted. ;-)
>
>> We probably should allow "commit -F -" to read from the standard
>> input if we already don't, but that is about as far as I am
>> willing to go at this moment.
>
> We do. So apparently the solution to my usage issue is:
>
> $ fmt -w 60 | git commit -F-
> This is my message.
>
> This is the body. Etc....
> EOF
>
> I'm thinking that's too much work for me.
If we supported multiple -m (presumably each becomes a single line?)
with internal fmt, I do not see how it would become less work.
$ git commit -w60 -m "This is my message." \
-m '' \
-m 'This is the body. Etc....'
looks more typing to me, even without the second line to force
the empty line between the summary and the body.
next prev parent reply other threads:[~2006-05-30 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 8:57 [PATCH] Automatically line wrap long commit messages Shawn Pearce
2006-05-29 9:00 ` Jan-Benedict Glaw
2006-05-29 9:14 ` Shawn Pearce
2006-05-29 9:16 ` Junio C Hamano
2006-05-29 9:46 ` Shawn Pearce
2006-05-30 8:38 ` Junio C Hamano [this message]
2006-05-31 2:18 ` Shawn Pearce
2006-05-31 5:05 ` Junio C Hamano
2006-06-01 3:34 ` Shawn Pearce
2006-06-01 6:37 ` 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=7vhd373o15.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).