git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC, PATCH] git send-email: Make --no-chain-reply-to the default
Date: Tue, 10 Nov 2009 06:22:11 +0100	[thread overview]
Message-ID: <20091110052211.GK7897@elte.hu> (raw)
In-Reply-To: <76718490911092112v4d1e7761ue98def756ed0d93b@mail.gmail.com>


* Jay Soffian <jaysoffian@gmail.com> wrote:

> On Mon, Nov 9, 2009 at 11:08 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > So ... the question would be ... could git-send-email flip its default
> 
> This is already in next for 1.7.0. See 41fe87f.
> 
> >From Junio's What's Cooking messages:
> 
> * jc/1.7.0-send-email-no-thread-default (2009-08-22) 1 commit
>   (merged to 'next' on 2009-08-22 at 5106de8)

Ah, awesome!

+1 for putting it into a .1.6.x stable branch too. (Unless there's a 
case where the recursive threading is actually useful and is being 
relied on.)

	Ingo

  reply	other threads:[~2009-11-10  5:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1257786206-9208-1-git-send-email-mitake@dcl.info.waseda.ac.jp>
     [not found] ` <1257789555.4108.348.camel@laptop>
2009-11-10  4:08   ` [RFC, PATCH] git send-email: Make --no-chain-reply-to the default Ingo Molnar
2009-11-10  5:12     ` Jay Soffian
2009-11-10  5:22       ` Ingo Molnar [this message]
2009-11-10  6:05         ` Junio C Hamano
2009-11-10  5:29     ` Junio C Hamano
2009-11-10  7:19       ` Ingo Molnar
2009-11-10 18:29         ` Ingo Molnar
2009-11-10  7:32     ` Peter Zijlstra
2009-11-10 19:46       ` Michael Witten
2009-11-10 19:58         ` Peter Zijlstra

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=20091110052211.GK7897@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@gmail.com \
    --cc=peterz@infradead.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).