From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git-fmt-merge-msg cleanup
Date: Wed, 08 Mar 2006 18:27:51 -0800 [thread overview]
Message-ID: <7vzmk0fj2w.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0603081753270.32577@g5.osdl.org> (Linus Torvalds's message of "Wed, 8 Mar 2006 17:56:07 -0800 (PST)")
Linus Torvalds <torvalds@osdl.org> writes:
> Since I've started using the "merge.summary" flag in my repo, my merge
> messages look nicer, but I dislike how I get notifications of merges
> within merges.
>
> So I'd suggest this trivial change..
Makes sense. Thanks.
prev parent reply other threads:[~2006-03-09 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 1:56 git-fmt-merge-msg cleanup Linus Torvalds
2006-03-09 2:27 ` Junio C Hamano [this message]
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=7vzmk0fj2w.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox