All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 patches for v3.4 take 2
Date: Wed, 29 Feb 2012 13:14:35 +0000	[thread overview]
Message-ID: <201202291314.36196.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdbr5X8KLiragbpk0VH5s+uo5T3C+e6AsNHk+x6s80YJ4w@mail.gmail.com>

On Wednesday 29 February 2012, Linus Walleij wrote:
> On Mon, Feb 27, 2012 at 10:02 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 27 February 2012, Linus Walleij wrote:
> >> On Fri, Feb 24, 2012 at 5:39 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> > On Friday 24 February 2012, Linus Walleij wrote:
> >> >> are available in the git repository at:
> >> >>   / ..BRANCH.NOT.VERIFIED..
> >> >
> >> > Something wrong on your end apparently.
> >>
> >> Hm :-( I'll check it by pulling it back myself next time.
> >
> > git request-pull checks this already, you just have to make sure that the right
> > branch or tag shows up in the pull URL.
> 
> Hm I think we simply hit "propagated to some mirrors but not all"
> so I saw the branch on my mirror but it wasn't yet up on yours :-/

I'm not convinced we're talking about the same thing here. I'm pretty sure
it was visible on my mirror, but not on yours, hence the
'..BRANCH.NOT.VERIFIED..'.

As I said, git request-pull will look at the remote to figure out which
branch name to put into the text, but it could not find the commit id on
the server when you ran it.
I could of course try to guess which branch you want me to pull, but
I'd rather hear it from you ;-)


	Arnd

      reply	other threads:[~2012-02-29 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 16:07 [GIT PULL] ux500 patches for v3.4 take 2 Linus Walleij
2012-02-24 16:39 ` Arnd Bergmann
2012-02-27  7:42   ` Linus Walleij
2012-02-27  9:02     ` Arnd Bergmann
2012-02-29  9:45       ` Linus Walleij
2012-02-29 13:14         ` Arnd Bergmann [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=201202291314.36196.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.