From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sean <seanlkml@sympatico.ca>, Jaroslav Kysela <perex@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: ALSA official git repository
Date: Fri, 27 May 2005 11:47:21 -0700 [thread overview]
Message-ID: <7vvf54y092.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0505271026020.17402@ppc970.osdl.org> (Linus Torvalds's message of "Fri, 27 May 2005 10:28:44 -0700 (PDT)")
>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:
LT> On Fri, 27 May 2005, Sean wrote:
>> >
>> > Now, arguably gitweb should ignore whitespace at the beginning, but
>> > equally arguably your commits shouldn't have them either...
>>
>> Perhaps git should enforce this? Patch attached.
>>
>> Remove leading empty lines from commit messages.
>>
>> Signed-off-by: Sean Estabrooks <seanlkml@sympatico.ca>
LT> I'm not sure.
LT> Opinions?
Porcelains and gitweb should play with each other nicely, but
the core should _not_ care by default.
An extra option ("--text", perhaps) to git-commit-tree is
acceptable to me, and it may be even a good thing to have. It
would make life a bit easiear for Porcelain writers if nothing
else. If that is to happen, I would say we could do more than
just leading blank line removal. We can also remove trailing
blanks before each LF, tabify indented log message contents, and
remove empty lines before EOF.
next prev parent reply other threads:[~2005-05-27 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 15:51 ALSA official git repository Jaroslav Kysela
2005-05-27 16:13 ` Linus Torvalds
2005-05-27 17:00 ` Sean
2005-05-27 17:28 ` Linus Torvalds
2005-05-27 18:47 ` Junio C Hamano [this message]
2005-05-27 17:43 ` Jaroslav Kysela
2005-05-27 18:16 ` Linus Torvalds
2005-05-27 20:51 ` Andrew Morton
2005-05-27 20:57 ` Junio C Hamano
2005-05-27 21:18 ` Jesper Juhl
2005-05-27 21:19 ` Schneelocke
2005-05-27 22:06 ` Linus Torvalds
2005-05-27 22:46 ` Andrew Morton
2005-05-28 2:21 ` Linus Torvalds
2005-05-28 3:33 ` Chris Wedgwood
2005-05-29 9:06 ` Jaroslav Kysela
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=7vvf54y092.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=seanlkml@sympatico.ca \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.