From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm-soc fixes for v3.9-rc3
Date: Mon, 18 Mar 2013 15:54:55 +0000 [thread overview]
Message-ID: <201303181554.55853.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFx9NF-+dt5r_hOpUfZxd6Ky+OBL2echeeM50ZE6UAaAdA@mail.gmail.com>
On Monday 18 March 2013, Linus Torvalds wrote:
> On Mon, Mar 18, 2013 at 7:22 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > are available in the git repository at:
> >
> > git+ssh://gitolite at ra.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/fixes
>
> What the heck happened to your script?
>
> Please use the public address so that others could look at it if they
> want to (and so that my merge messages make sense in a public
> setting).
>
> I fixed it up, but please fix your script for next time.
Thanks for fixing it up, it was no script this time, but a manual copy-paste
mistake. git-request-pull got confused by the fact I had commits both before
and after -rc2 in the branch, and was listing lots of changes that you had
already merged in the list, so I tried to construct the output in the
way that was supposed to look, and failed.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arm@kernel.org" <arm@kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arm-soc fixes for v3.9-rc3
Date: Mon, 18 Mar 2013 15:54:55 +0000 [thread overview]
Message-ID: <201303181554.55853.arnd@arndb.de> (raw)
In-Reply-To: <CA+55aFx9NF-+dt5r_hOpUfZxd6Ky+OBL2echeeM50ZE6UAaAdA@mail.gmail.com>
On Monday 18 March 2013, Linus Torvalds wrote:
> On Mon, Mar 18, 2013 at 7:22 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > are available in the git repository at:
> >
> > git+ssh://gitolite@ra.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/fixes
>
> What the heck happened to your script?
>
> Please use the public address so that others could look at it if they
> want to (and so that my merge messages make sense in a public
> setting).
>
> I fixed it up, but please fix your script for next time.
Thanks for fixing it up, it was no script this time, but a manual copy-paste
mistake. git-request-pull got confused by the fact I had commits both before
and after -rc2 in the branch, and was listing lots of changes that you had
already merged in the list, so I tried to construct the output in the
way that was supposed to look, and failed.
Arnd
next prev parent reply other threads:[~2013-03-18 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 14:22 [GIT PULL] arm-soc fixes for v3.9-rc3 Arnd Bergmann
2013-03-18 14:22 ` Arnd Bergmann
2013-03-18 15:30 ` Linus Torvalds
2013-03-18 15:30 ` Linus Torvalds
2013-03-18 15:54 ` Arnd Bergmann [this message]
2013-03-18 15:54 ` Arnd Bergmann
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=201303181554.55853.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.