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.
Date: Thu, 12 Jan 2012 23:16:29 -0400 [thread overview]
Message-ID: <87vcogs35e.fsf@zancas.localnet> (raw)
In-Reply-To: <87fwfkluh3.fsf@praet.org>
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
next prev parent reply other threads:[~2012-01-13 3:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 23:45 [PATCH] Output unmodified Content-Type header value for JSON format Dmitry Kurochkin
2011-11-19 1:58 ` Jameson Graef Rollins
2011-11-19 2:42 ` Dmitry Kurochkin
2011-11-19 4:59 ` Austin Clements
2011-11-19 5:26 ` Dmitry Kurochkin
2011-11-19 18:58 ` Austin Clements
2011-11-20 18:52 ` Dmitry Kurochkin
2011-11-19 10:49 ` Jameson Graef Rollins
2011-11-20 18:32 ` Dmitry Kurochkin
2011-11-20 20:10 ` Jameson Graef Rollins
2011-11-23 3:40 ` Austin Clements
2012-01-12 17:07 ` Pieter Praet
2012-01-12 17:28 ` Austin Clements
2012-01-14 9:19 ` Pieter Praet
2012-01-15 11:52 ` David Edmondson
2012-01-15 17:58 ` Austin Clements
2012-01-16 8:49 ` David Edmondson
2012-01-16 13:18 ` Tomi Ollila
2011-11-19 4:18 ` [PATCH v2] " Dmitry Kurochkin
2011-11-19 12:59 ` David Bremner
2011-11-20 18:35 ` Dmitry Kurochkin
2012-01-12 17:08 ` Pieter Praet
2012-01-13 3:16 ` David Bremner [this message]
2012-01-14 8:59 ` Pieter Praet
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcogs35e.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=pieter@praet.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).