Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/6] support/testing/tests/core: SSP & hardening flags
Date: Tue, 17 Jul 2018 13:28:48 +0200	[thread overview]
Message-ID: <20180717132848.0a9d7e0c@windsurf> (raw)
In-Reply-To: <CANQCQpb1cH1k7NBDuRxfs=cKD4=0AgoS100yR7zxwSapnZyRzw@mail.gmail.com>

Hello,

On Tue, 17 Jul 2018 06:25:28 -0500, Matthew Weber wrote:

> > I'm a bit confused by this patch coming alone, outside of any series.
> > Is it just because you had only changes to this PATCH 6/6 that you
> > didn't resent the full series ?  
> 
> Understood, yeah I should have asked on IRC today before sending.  I
> already had reviewed by on the other patches so I hesitated resending
> them as there wasn't change. Generally, can I add reviewed by's on
> patches that don't change on a sending of a new version as long as the
> patch didn't change?

It's not only that you "can", it's that you "should" so that just
Reviewed-by are not lost.

Of course, if you make changes to the patches, you cannot keep the
Reviewed-by because it may not hold anymore (except if the changes are
really tiny/trivial).

> > In general, my preference is that a full series gets resent, because it
> > is obvious what your intention is. By just resending one patch, I
> > wonder if you really sent that one patch, or if all patches were sent,
> > but the previous ones were lost/not received for some reason.
> 
> Agree, it does make it confusing.  My intent was just to update this
> one as the rest were in a good state without resending and had review.
> Do you want me to resent the complete set?

No need to do that for this one. But in general, my preference goes to
receiving the full series for each iteration. Yes it creates more
noise/traffic on the mailing list, but it makes perfectly clear what is
intended, which to me is more important.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-17 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  3:04 [Buildroot] [PATCH v2 6/6] support/testing/tests/core: SSP & hardening flags Matt Weber
2018-07-17  8:06 ` Thomas Petazzoni
2018-07-17 11:25   ` Matthew Weber
2018-07-17 11:28     ` Thomas Petazzoni [this message]
2018-07-18  0:20 ` Ricardo Martincoski
2018-08-10 21:18 ` Thomas Petazzoni
2018-08-11  0:49   ` Matthew Weber

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=20180717132848.0a9d7e0c@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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