From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] gitweb: Add committags support
Date: Tue, 26 Sep 2006 13:52:59 +0200 [thread overview]
Message-ID: <efb4an$lg9$1@sea.gmane.org> (raw)
In-Reply-To: 20060925201500.GG20017@pasky.or.cz
Petr Baudis wrote:
> Dear diary, on Mon, Sep 25, 2006 at 08:06:44PM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
>> So when putting message if into commit message, just put the commit
>> message in separate line, perhaps even with some indentation, like
>> below:
>> Msg-Id: <200609231533.02455.jnareb@gmail.com>
>
> Oh please. :-) The tool should bend, not the user.
Still it is more (much more) readable to have Msg-Id "header" (or
equivalent), and message id itself in one line.
> Are you going to mandate that for bug references as well? Or should I
> proofread all of my commits (if they aren't actually just autoformatted
> by fmt without my further review) to verify that they don't actually end
> up wrapped, and manually reformat the whole paragraph?
O.K. that convinces me (although wrapped hyperlink is not a pretty thing).
Besides for tags we have natural multiline "tag", namely PGP signature,
which we wpuld (most probably) want to syntax highlight wrapping it in
<div class="GPG_signature">...</div> element.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-26 11:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 21:56 [RFC/PATCH] gitweb: Add committags support Jakub Narebski
2006-09-22 17:55 ` Jakub Narebski
2006-09-23 3:29 ` Petr Baudis
2006-09-23 8:34 ` Jakub Narebski
2006-09-23 12:11 ` Petr Baudis
2006-09-23 13:33 ` Jakub Narebski
2006-09-23 14:05 ` Petr Baudis
2006-09-25 18:06 ` Jakub Narebski
2006-09-25 20:15 ` Petr Baudis
2006-09-26 11:52 ` Jakub Narebski [this message]
2006-09-23 19:58 ` Junio C Hamano
2006-09-23 20:18 ` Jakub Narebski
2006-09-23 20:50 ` Junio C Hamano
2006-09-24 9:37 ` Jakub Narebski
2006-09-24 10:34 ` Junio C Hamano
2006-09-24 16:35 ` Jakub Narebski
2006-09-24 19:17 ` 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='efb4an$lg9$1@sea.gmane.org' \
--to=jnareb@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).