From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
linux-kernel@vger.kernel.org,
"Mark A. Greer" <mgreer@animalcreek.com>,
arm@kernel.org, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL 00/15] arm-soc: changes for v3.6
Date: Tue, 24 Jul 2012 12:00:10 +0000 [thread overview]
Message-ID: <201207241200.11190.arnd@arndb.de> (raw)
In-Reply-To: <20120724081246.GS6522@atomide.com>
On Tuesday 24 July 2012, Tony Lindgren wrote:
> > I spent too much time fiddling with my scripts again in an attempt to
> > get closer to the regular git-request-pull version. The older version
> > got this right, but unfortunately I removed the part where I manually
> > print the right pull address because that had caused other problems
> > before.
>
> FYI, this issue happens also with git request-pull if the tag has not
> yet gotten mirrored but the branch is already mirrored.
In this case it they were both there, but it picked up the branch
anyway. I actually made sure that the tag description was included
by git-request-pull, and the tag has a different name from the
branch (no "next/" prefix), but the tool is not does not attempt
to pick up the tag rather than the branch when both are available.
Apparently, the problem is that it treats the branch "next/foo"
as as exact match for a pull request on the "foo" tag even when
that tag is present as "foo" on the server. If I either name the
branch or the tag differently, or pass "tags/foo" as the
argument to git-request-pull, it reports back the tag instead.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 00/15] arm-soc: changes for v3.6
Date: Tue, 24 Jul 2012 12:00:10 +0000 [thread overview]
Message-ID: <201207241200.11190.arnd@arndb.de> (raw)
In-Reply-To: <20120724081246.GS6522@atomide.com>
On Tuesday 24 July 2012, Tony Lindgren wrote:
> > I spent too much time fiddling with my scripts again in an attempt to
> > get closer to the regular git-request-pull version. The older version
> > got this right, but unfortunately I removed the part where I manually
> > print the right pull address because that had caused other problems
> > before.
>
> FYI, this issue happens also with git request-pull if the tag has not
> yet gotten mirrored but the branch is already mirrored.
In this case it they were both there, but it picked up the branch
anyway. I actually made sure that the tag description was included
by git-request-pull, and the tag has a different name from the
branch (no "next/" prefix), but the tool is not does not attempt
to pick up the tag rather than the branch when both are available.
Apparently, the problem is that it treats the branch "next/foo"
as as exact match for a pull request on the "foo" tag even when
that tag is present as "foo" on the server. If I either name the
branch or the tag differently, or pass "tags/foo" as the
argument to git-request-pull, it reports back the tag instead.
Arnd
next prev parent reply other threads:[~2012-07-24 12:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 20:32 [GIT PULL 00/15] arm-soc: changes for v3.6 Arnd Bergmann
2012-07-23 20:32 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 01/15] arm-soc: non-critical bug fixes Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 02/15] arm-soc: general cleanups Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 03/15] arm-soc: soc-specific updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 04/15] arm-soc: samsung dma changes Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 05/15] arm-soc: device tree description updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 06/15] arm-soc: spi updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 07/15] arm-soc: timer updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 08/15] arm-soc: cleanups, part 2 Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 09/15] arm-soc: new SoC support Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 10/15] arm-soc: defconfig updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 11/15] arm-soc: board specific updates Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 12/15] arm-soc: sparse IRQ conversion Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 13/15] arm-soc: pincontrol drivers Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 14/15] arm-soc: power management changes Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-23 20:32 ` [GIT PULL 15/15] arm-soc: clk changes Arnd Bergmann
2012-07-23 20:33 ` Arnd Bergmann
2012-07-24 1:03 ` [GIT PULL 00/15] arm-soc: changes for v3.6 Linus Torvalds
2012-07-24 1:03 ` Linus Torvalds
2012-07-24 7:51 ` Arnd Bergmann
2012-07-24 7:51 ` Arnd Bergmann
2012-07-24 8:12 ` Tony Lindgren
2012-07-24 8:12 ` Tony Lindgren
2012-07-24 12:00 ` Arnd Bergmann [this message]
2012-07-24 12:00 ` Arnd Bergmann
2012-07-24 20:51 ` Paul Walmsley
2012-07-24 20:51 ` Paul Walmsley
2012-07-26 23:10 ` Mark A. Greer
2012-07-26 23:10 ` Mark A. Greer
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=201207241200.11190.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.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.