From: Jeff Cody <jcody@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Paul Burton <paul.burton@imgtec.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
Leon Alrae <leon.alrae@imgtec.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU dtc submodule
Date: Mon, 26 Sep 2016 00:51:41 -0400 [thread overview]
Message-ID: <20160926045141.GA2695@localhost.localdomain> (raw)
In-Reply-To: <20160924012118.GB4842@umbus.fritz.box>
On Sat, Sep 24, 2016 at 11:21:18AM +1000, David Gibson wrote:
> On Fri, Sep 23, 2016 at 03:23:26PM +0100, Paul Burton wrote:
> > On Friday, 23 September 2016 09:13:51 BST Jeff Cody wrote:
> > > > Leon: Please give the git URL and branch that should be mirrored. It
> > > > cannot be a tag since that is immutable. Instead it should be the
> > > > dtc development/release tree that will be updated in the future.
> > >
> > > Yes, once I get the git URL I'll update it on the server. I presume it is
> > > 'master' on git://git.kernel.org/pub/scm/utils/dtc/dtc.git, but I will wait
> > > for confirmation before I do anything.
> > >
> > > Thanks,
> > > Jeff
> >
> > Hi Jeff,
> >
> > That would be the right branch for DTC, but sadly the master branch doesn't contain the
> > actual commit that was tagged as the v1.4.2 release. v1.4.2 tags this commit:
> >
> > https://git.kernel.org/cgit/utils/dtc/dtc.git/commit/?
> > h=v1.4.2&id=ec02b34c05be04f249ffaaca4b666f5246877dea[1]
> >
> > Its parent commit is in the master branch, but it isn't. So simply mirroring the master
> > branch wouldn't be enough, you'd need to include the v1.4.2 tag specifically. I've CC'd David
> > Gibson who tagged DTC v1.4.2 in case he has input or can rectify this (which would
> > probably be either a rebase & force push of the last 2 commits on the master branch atop
> > v1.4.2, or a new release).
>
> Oops.. that's my mistake (with my upstream dtc maintainer hat on).
>
> Not sure quite how I managed that, but yes, master branches off just
> before the v1.4.2 release, instead of just after. I've merged them
> back together now, so that master should include v1.4.2 now.
>
Thanks,
I've updated the git server, and submitted a patch to move the QEMU dtc
submodule version to 1.4.2.
Thanks,
Jeff
prev parent reply other threads:[~2016-09-26 4:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 11:44 [Qemu-devel] QEMU dtc submodule Leon Alrae
2016-09-22 8:11 ` Thomas Huth
2016-09-22 8:42 ` Alexander Graf
2016-09-23 13:04 ` Stefan Hajnoczi
2016-09-23 13:13 ` Jeff Cody
2016-09-23 14:23 ` Paul Burton
2016-09-24 1:21 ` David Gibson
2016-09-26 4:51 ` Jeff Cody [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=20160926045141.GA2695@localhost.localdomain \
--to=jcody@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=leon.alrae@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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.