From: Martin Waitz <tali@admingilde.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: Topic descriptions
Date: Thu, 7 Dec 2006 12:55:52 +0100 [thread overview]
Message-ID: <20061207115552.GC10468@admingilde.org> (raw)
In-Reply-To: <7v4ps8y7un.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
hoi :)
On Wed, Dec 06, 2006 at 02:31:28PM -0800, Junio C Hamano wrote:
> But that description thing would be useful in gitweb, for
> example.
And it could be useful to automatically generate the summary for
please-pull mails or for the [0/N] patch introduction mail.
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-07 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:53 Topic descriptions Andy Parkins
2006-12-06 22:31 ` Junio C Hamano
2006-12-07 8:37 ` Andy Parkins
2006-12-07 9:34 ` Junio C Hamano
2006-12-07 10:45 ` Robin Rosenberg
2006-12-07 11:55 ` Martin Waitz [this message]
2006-12-09 1:11 ` Sam Vilain
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=20061207115552.GC10468@admingilde.org \
--to=tali@admingilde.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).