public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] xfs: updates for 4.7-rc1
Date: Fri, 27 May 2016 10:13:14 +1000	[thread overview]
Message-ID: <20160527001314.GI26977@dastard> (raw)
In-Reply-To: <CA+55aFydXfyKUiCA7FEXOhPuoQJrAMY+K-U+n7iGaKHSCYHFSA@mail.gmail.com>

On Thu, May 26, 2016 at 10:19:13AM -0700, Linus Torvalds wrote:
> On Wed, May 25, 2016 at 11:13 PM, Dave Chinner <david@fromorbit.com> wrote:
> >
> > Just yell if this is not OK and I'll drop those branches for this
> > merge and resend the pull request....
> 
> i'm ok with the late branches, it's not like xfs has been a problem spot.

Still, I'll try to avoid them because it reduces testing time.

> However:
> 
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git for-next
> 
> Your pull request mentions the 'for-next' branch, but I think you
> *meant* to send me the "xfs-for-linus-4.7-rc1" tag which points to the
> same commit and has your summary in it.

<sigh>

Mea culpa. I ran this command after creating the tag:

$ git request-pull v4.6 git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git tags/xfs-for-linus-4.7-rc1 > ~/tmp/t.txt

And I didn't check the output closely enough. I forgot to push the
tag to the upstream repo before running request-pull.

Git often makes it very easy to make mistakes whilst simultaneously
making it hard to notice you've made a mistake. :(

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2016-05-27  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  6:13 [GIT PULL] xfs: updates for 4.7-rc1 Dave Chinner
2016-05-26 17:19 ` Linus Torvalds
2016-05-27  0:13   ` Dave Chinner [this message]
2016-05-27  2:05     ` Linus Torvalds
2016-05-30  5:23       ` Dave Chinner

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=20160527001314.GI26977@dastard \
    --to=david@fromorbit.com \
    --cc=akpm@linux-foundation.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