From: David Bremner <david@tethera.net>
To: Pieter Praet <pieter@praet.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2] Output unmodified Content-Type header value for JSON
	format.
In-Reply-To: <87fwfkluh3.fsf@praet.org>
References: <1321659905-24367-1-git-send-email-dmitry.kurochkin@gmail.com>
	<1321676321-27745-1-git-send-email-dmitry.kurochkin@gmail.com>
	<87sjlktgi6.fsf@zancas.localnet> <87obw6prpd.fsf@gmail.com>
	<87fwfkluh3.fsf@praet.org>
User-Agent: Notmuch/0.10.2+177~g38546e4 (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Thu, 12 Jan 2012 23:16:29 -0400
Message-ID: <87vcogs35e.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Precedence: list

On Thu, 12 Jan 2012 18:08:08 +0100, Pieter Praet <pieter@praet.org> wrote:
> > > - The previous point is a bit of a counterargument to this, but in

> > I couls separate it.  I made is a single patch to avoid having a
> > revision with broken emacs UI (and tests).
> > 

> I'd like to propose to always apply patch series on a *topic* branch
> which would then be merged back into 'master', thus avoiding this issue
> altogether whilst making it more obvious which patches belong together
> (eg. for easier cross-referencing with the ML).

Hi Pieter;

Sorry, I must have lost the thread somewhere.  What application are you
thinking about, and what issue do you think that topic branches avoid?

d