From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: Josh Triplett <josht@us.ibm.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/3] git-format-patch: Make the second and subsequent mails replies to the first
Date: Sat, 15 Jul 2006 09:45:32 +0200 [thread overview]
Message-ID: <20060715074532.GF13776@pasky.or.cz> (raw)
In-Reply-To: <7vwtagnfsk.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Fri, Jul 14, 2006 at 09:32:27PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> said that...
> Josh Triplett <josht@us.ibm.com> writes:
>
> > ..., but you
> > suggested that you didn't mind having threading as the default.
>
> Did I? ... then that was either a mistake or miscommunication.
>
> I do mind changing the default output. I do not mind threading
> as the default ONLY IF user asks for output with these extra
> headers.
What's the big deal? It's not like we didn't change those things in the
past if it doesn't horribly break everything and the new behaviour is
clearly more sensible.
It would be good to know what the general policy on this is nowadays.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
next prev parent reply other threads:[~2006-07-15 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 15:44 [PATCH] git-format-patch: Make the second and subsequent mails replies to the first Josh Triplett
2006-07-10 16:01 ` Johannes Schindelin
2006-07-10 16:29 ` Erik Mouw
2006-07-10 16:43 ` Josh Triplett
2006-07-10 20:25 ` Jakub Narebski
2006-07-10 18:41 ` [PATCH 1/3] " Josh Triplett
2006-07-10 21:44 ` Junio C Hamano
2006-07-14 17:16 ` Josh Triplett
2006-07-14 18:23 ` Junio C Hamano
2006-07-14 19:20 ` Josh Triplett
2006-07-14 19:32 ` Junio C Hamano
2006-07-15 7:45 ` Petr Baudis [this message]
2006-07-15 8:10 ` 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=20060715074532.GF13776@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=josht@us.ibm.com \
--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).