qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Clark <mjc@sifive.com>,
	Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
	Palmer Dabbelt <palmer@sifive.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Sagar Karandikar <sagark@eecs.berkeley.edu>,
	RISC-V Patches <patches@groups.riscv.org>
Subject: Re: [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2
Date: Thu, 8 Mar 2018 11:36:30 +0000	[thread overview]
Message-ID: <20180308113630.GL4718@redhat.com> (raw)
In-Reply-To: <CAFEAcA9xMj_Wq_mxJU-vhUDidUKk+UVtCNGeGK-Hx_bcqkjMug@mail.gmail.com>

On Thu, Mar 08, 2018 at 11:19:30AM +0000, Peter Maydell wrote:
> On 8 March 2018 at 11:10, Michael Clark <mjc@sifive.com> wrote:
> >
> > On Thu, 8 Mar 2018 at 11:02 PM, Peter Maydell <peter.maydell@linaro.org>
> > wrote:
> >>
> >> On 6 March 2018 at 19:46, Michael Clark <mjc@sifive.com> wrote:
> >> > -----BEGIN PGP SIGNED MESSAGE-----
> >> > Hash: SHA1
> >> >
> >> > The following changes since commit
> >> > f32408f3b472a088467474ab152be3b6285b2d7b:
> >> >
> >> >   misc: don't use hwaddr as a type in trace events (2018-03-06 14:24:30
> >> > +0000)
> >> >
> >> > are available in the git repository at:
> >> >
> >> >   https://github.com/riscv/riscv-qemu.git tags/riscv-qemu-upstream-v8.2
> >> >
> >> > for you to fetch changes up to 7051b081bf6796e5e84406f6223a7c4900bf7298:
> >> >
> >> >   RISC-V - Remove support for adhoc non-standard X_COP local-interrupt
> >> > (2018-03-07 08:36:03 +1300)
> >>
> >>
> >> Hi -- I would have applied this, but some of the commits
> >> have no signed-off-by lines.
> >>
> >> This is important, and I've already asked for it once. We cannot
> >> accept anything that doesn't have a clear record in the commit
> >> message of everybody (person or company) who's contributed code
> >> to it, indicating that they're happy for their copyrighted
> >> contributions to be taken into QEMU under our license. Lists
> >> of names without emails in the cover letter are not sufficient.
> >>
> >> In fact a lot of the last part of this patchset looks like
> >> unreviewed changes/fixes that if we were going to have them we
> >> should have squashed into the correct patches and resent the
> >> series for review. Please don't do this. Code review is an
> >> important part of how the QEMU project works.
> >
> >
> > You must be looking at the wrong tag. There are multiple sign-offs in all 23
> > commits. The tag is riscv-qemu-upstream-v8.2. Sagar and Bastian contacted me
> > out of band to add their sign-offs. Please look at the commits again and
> > tell me which commit id doesn’t have a sign-off on that tag (23 commits
> > iirc)
> 
> I'm looking at the one this email tells me to pull:
>   https://github.com/riscv/riscv-qemu.git tags/riscv-qemu-upstream-v8.2
>   changes up to 7051b081bf6796e5e84406f6223a7c4900bf7298
> 
> Commit 7051b081bf6796e5e84406f6223a7c4900bf7298,
> 9390ed5f4ca5fd3bde10ee2dcf4e7d915d1c189d,
> b38548c4057fb670950a4b94efe5c03b8aba4118,
> etc etc all have no signoff.

There's something peculiar going on when fetching the PR.

I did a 'git fetch riscv/riscv-qemu-upstream-v8.2' which pulled into
FETCH_HEAD. If i do 'git log FETCH_HEAD' then I see those commits
you mention as missing signoff.  If I instead do 'git log riscv-qemu-upstream-v8.2'
then all the commits have signoffs - it ranges 
4dc62b15323bb6338c4b426f76e92be55f87db8c...25fa194b7b11901561532e435beb83d046899f7a.

I'm confused why pulling the tag is populating extra commits into
FETCH_HEAD, that are seemingly not part of the tag.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-03-08 11:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 19:46 [Qemu-devel] [PULL] RISC-V QEMU Port Submission v8.2 Michael Clark
2018-03-07  0:09 ` Michael Clark
2018-03-07 10:11   ` Richard W.M. Jones
2018-03-07 12:15     ` Michael Clark
2018-03-08 10:02 ` Peter Maydell
2018-03-08 11:10   ` Michael Clark
2018-03-08 11:18     ` Michael Clark
2018-03-08 11:41       ` Michael Clark
2018-03-08 11:52         ` Stefan Hajnoczi
2018-03-08 19:29         ` [Qemu-devel] [patches] " Palmer Dabbelt
2018-03-08 19:53           ` Michael Clark
2018-03-09 14:28             ` Peter Maydell
2018-03-09 14:51               ` Michael Clark
2018-03-09 15:15                 ` Alex Bennée
2018-03-09 15:22                   ` Peter Maydell
2018-03-09 16:49               ` Peter Maydell
2018-03-09 20:11                 ` Michael Clark
2018-03-09 20:23                   ` Michael Clark
2018-03-08 11:48       ` [Qemu-devel] " Daniel P. Berrangé
2018-03-08 20:03         ` Michael Clark
2018-03-08 11:49       ` Paolo Bonzini
2018-03-08 11:19     ` Peter Maydell
2018-03-08 11:36       ` Daniel P. Berrangé [this message]
2018-03-08 11:33     ` Daniel P. Berrangé
2018-03-08 11:42       ` Daniel P. Berrangé
2018-03-08 12:25 ` Daniel P. Berrangé
2018-03-08 12:39   ` Paolo Bonzini

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=20180308113630.GL4718@redhat.com \
    --to=berrange@redhat.com \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=mjc@sifive.com \
    --cc=palmer@sifive.com \
    --cc=patches@groups.riscv.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sagark@eecs.berkeley.edu \
    /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;
as well as URLs for NNTP newsgroup(s).