Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	IDE-ML <linux-ide@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [GIT PULL] libata fixes for v3.16-rc6
Date: Mon, 21 Jul 2014 14:33:22 -0400	[thread overview]
Message-ID: <20140721183322.GA29601@mtj.dyndns.org> (raw)
In-Reply-To: <CA+55aFwzZoef-fXj1D57N9ywxWBF0bj2cWgOQMQDLM=NAH7hrA@mail.gmail.com>

Hello, Linus.

On Mon, Jul 21, 2014 at 11:27:18AM -0700, Linus Torvalds wrote:
> On Mon, Jul 21, 2014 at 5:17 AM, Tejun Heo <tj@kernel.org> wrote:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git
> >
> > for you to fetch changes up to b32bfc06aefab61acc872dec3222624e6cd867ed:
> 
> Nope, nothing like that there.
> 
> Did you perhaps mean for me to pull the "for-3.16-fixes" branch?
> Because that does indeed match what you are speaking of...
> 
> I pulled the correct branch, but please, please, *please* fix your
> scripts to have the right branch name.

Urgh... sorry about that.  This is the same git-request-pull problem
that occurred the last time.  I forgot adding cc:stable to the last
patch and force-pushed that out before generating the pull request (I
had it sitting in my local branch for some days) and git-request-pull
dropped the branch name because the commit IDs of local and remote
disagreed.  git --version says 1.9.3.  Maybe it's not fixed in this
version yet?

Thanks.

-- 
tejun

  reply	other threads:[~2014-07-21 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 12:17 [GIT PULL] libata fixes for v3.16-rc6 Tejun Heo
2014-07-21 18:27 ` Linus Torvalds
2014-07-21 18:33   ` Tejun Heo [this message]
2014-07-21 18:44     ` Linus Torvalds

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=20140721183322.GA29601@mtj.dyndns.org \
    --to=tj@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox