[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160527001314.GI26977@dastard>
Date: Fri, 27 May 2016 10:13:14 +1000
From: Dave Chinner <david@...morbit.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] xfs: updates for 4.7-rc1
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@...morbit.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@...morbit.com
Powered by blists - more mailing lists