From: Michael Ellerman <mpe@ellerman.id.au>
To: David Vrabel <david.vrabel@citrix.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [GIT PULL] xen: features and fixes for 4.5-rc0
Date: Wed, 13 Jan 2016 19:48:25 +1100 [thread overview]
Message-ID: <1452674905.7404.3.camel@ellerman.id.au> (raw)
In-Reply-To: <56951415.4030202@citrix.com>
On Tue, 2016-01-12 at 14:56 +0000, David Vrabel wrote:
> On 11/01/16 23:01, Stephen Rothwell wrote:
> > Hi David,
> >
> > On Mon, 11 Jan 2016 11:32:01 +0000 David Vrabel <dvrabel@cantab.net> wrote:
> > >
> > > Please git pull the following tag:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.5-rc0-tag
> > >
> > > xen: features and fixes for 4.5-rc0
> > >
> > > - - Stolen ticks and PV wallclock support for arm/arm64.
> > > - - Add grant copy ioctl to gntdev device.
> >
> > So the version I have of this in linux-next has not been updated since
> > Dec 2 and is based on v4.4-rc1. The version above is based on
> > v4.4-rc6 and has extra commits ... Did someone forget to update the
> > xen-tip/linux-next branch?
>
> Yes.
>
> Ideally I'd like the linux-next branch in ../xen/tip.git to be symbolic
> reference to the current for-linus-x.y branch so I do not have to
> remember to push to two different branches. I can't see a way to do
> this though.
You're using tags for the pull request though, so do you need the for-linus-x.y
branch at all?
I've stopped using them, and instead just push to next and ask Linus to pull
a tag. That also avoids any possibility of the for-linus-x.y branch getting out
of sync with the for-linus-x.y tag.
cheers
prev parent reply other threads:[~2016-01-13 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 11:32 David Vrabel
2016-01-11 23:01 ` Stephen Rothwell
2016-01-12 14:56 ` [Xen-devel] " David Vrabel
2016-01-13 8:48 ` Michael Ellerman [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=1452674905.7404.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=xen-devel@lists.xenproject.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
Powered by JetHome