From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>
Cc: Sam Ravnborg <sam@ravnborg•org>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: tip-core merge conflict
Date: Fri, 13 Jun 2008 00:34:27 +1000 [thread overview]
Message-ID: <20080613003427.9866ff07.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080612141022.GA28001@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
Hi Ingo,
On Thu, 12 Jun 2008 16:10:22 +0200 Ingo Molnar <mingo@elte•hu> wrote:
>
> i think it might be a communications issue - as conflicts are not a
> problem per se, they are just a complication that you resolve.
>
> So it might make sense to change the subject line of your merge
> resolution mails from:
>
> linux-next: tip-core merge conflict
>
> to:
>
> linux-next: manual merge of tip-core
>
> that way people still stay informed about interactions between trees
> (and can reduce them when they are avoidable, and can check the result
> as well since it was done manually), but dont see it as some sort of
> failure that needs to be 'resolved' via dropping patches.
Thanks for the suggestion, I like it. Look forward to calmer subjects
from now on. :-)
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-06-12 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 2:08 linux-next: tip-core merge conflict Stephen Rothwell
2008-06-10 4:51 ` Stephen Rothwell
2008-06-10 19:04 ` Sam Ravnborg
2008-06-10 23:52 ` Stephen Rothwell
2008-06-12 14:10 ` Ingo Molnar
2008-06-12 14:34 ` Stephen Rothwell [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=20080613003427.9866ff07.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=sam@ravnborg$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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