All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9] package/sysdig: New package
Date: Fri, 27 Mar 2015 22:57:20 +0100	[thread overview]
Message-ID: <5515D240.9070200@mind.be> (raw)
In-Reply-To: <CA+TH9Vn6t-bT78+Z8iGFq7X3ftnbZqk0-mzoQJgVODDLpQmG-Q@mail.gmail.com>

On 26/03/15 21:37, Angelo Compagnucci wrote:
> Dear Ryan Barnett,
> 
> 2015-03-26 19:38 GMT+01:00 Ryan Barnett <ryan.barnett@rockwellcollins.com>:
>> > Hi Angelo,
>> >
>> > On Thu, Mar 26, 2015 at 2:48 AM, Angelo Compagnucci
>> > <angelo.compagnucci@gmail.com> wrote:
>>> >> Sysdig is open source, system-level exploration:
>>> >> capture system state and activity from a running Linux
>>> >> instance, then save, filter and analyze.
>>> >>
>>> >> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>> >
>> > It would be good to carry forward previous reviews when you submit a
>> > new version of a patch. In your v8 of this patch Yegor Yefremov
>> > reviewed your patch so after your Signed-off-by line you should put
>> > this:
>> >
>> > Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com>
> Are you sure? IMO, If the patch changes it should be reviewed again.

 It basically depends on how much you still changed after that reviewed-by was
given. In this case, it indeed probably changed too much to keep the tag.

 For Yegor's convenience, however, it could be good to add something like:

Previous-version-reviewed-by: ...

(At least in my case, I tend to look more carefully at the patches I reviewed
before, and I tend to forget which ones I reviewed in the past.)


 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      parent reply	other threads:[~2015-03-27 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26  7:48 [Buildroot] [PATCH v9] package/sysdig: New package Angelo Compagnucci
2015-03-26 18:38 ` Ryan Barnett
2015-03-26 20:37   ` Angelo Compagnucci
2015-03-27  0:46     ` Ryan Barnett
2015-03-27 21:57     ` Arnout Vandecappelle [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=5515D240.9070200@mind.be \
    --to=arnout@mind.be \
    --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 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.