From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>,
James Hogan <james.hogan@imgtec.com>, Arnd <arnd@arndb.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] late arch/metag fixes for v3.9-rc1
Date: Sat, 2 Mar 2013 10:40:16 -0800 [thread overview]
Message-ID: <CA+55aFyTg5oxT-Sx65CF3RJaK8Ejyf7RvPSrTWv-bNV0Um-k+w@mail.gmail.com> (raw)
In-Reply-To: <20130302181025.GA15498@pd.tnic>
On Sat, Mar 2, 2013 at 10:10 AM, Borislav Petkov <bp@alien8.de> wrote:
>
> Hmm, so this comes up almost everytime new maintainers send stuff (and
> when seasoned maintainers forget :)), maybe we should hold it down
> somewhere in Documentation/ for future reference?
If somebody wants to edit it a bit for readability (and maybe try to
gather previous rants of mine), I'll happily take the patch.
And we should probably add some commentary from submaintainers too.
They often have their own issues. Some of them are the same "dammit, I
relied on a rebased tree of another", but I bet there are cross-merge
issues *within* submaintainerships too (eg there are some trees that I
pull that have their internal topic branches with multiple maintainers
where they merge between them, and some of them sometimes seem to have
a bit too much merging going on).
Linus
next prev parent reply other threads:[~2013-03-02 18:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:55 [GIT PULL] late arch/metag fixes for v3.9-rc1 James Hogan
2013-03-01 18:03 ` Linus Torvalds
2013-03-01 18:54 ` James Hogan
2013-03-02 10:22 ` James Hogan
2013-03-02 15:48 ` Stephen Rothwell
2013-03-02 16:22 ` James Hogan
2013-03-03 2:11 ` Stephen Rothwell
2013-03-02 16:28 ` Linus Torvalds
2013-03-02 16:31 ` Linus Torvalds
2013-03-02 18:10 ` Borislav Petkov
2013-03-02 18:40 ` Linus Torvalds [this message]
2013-03-02 19:19 ` Borislav Petkov
2013-03-02 19:25 ` Linus Torvalds
2013-03-02 19:06 ` Raymond Jennings
2013-03-02 19:05 ` James Hogan
2013-03-02 21:40 ` James Hogan
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=CA+55aFyTg5oxT-Sx65CF3RJaK8Ejyf7RvPSrTWv-bNV0Um-k+w@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).