All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] patman: Suppress duplicate signoffs only for real patches
Date: Thu, 15 May 2014 09:29:57 +0200	[thread overview]
Message-ID: <53746CF5.4050705@monstr.eu> (raw)
In-Reply-To: <1400004843-2306-1-git-send-email-sjg@chromium.org>

On 05/13/2014 08:14 PM, Simon Glass wrote:
> There is an unfortunate bug in the signoff suppression logic. The first
> pass is performed with 'git log', and all signoffs are added to the
> supression set, such that the second time (when processing the real
> patches) we always suppress the signoffs.
> 
> Correct this by only suppressing signoffs in the second pass.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>

I have seen the same problem as Masahiro.

Tested-by: Michal Simek <monstr@monstr.eu>

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140515/9d36a571/attachment.pgp>

  reply	other threads:[~2014-05-15  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 18:14 [U-Boot] [PATCH] patman: Suppress duplicate signoffs only for real patches Simon Glass
2014-05-15  7:29 ` Michal Simek [this message]
2014-05-16  9:49 ` Andreas Bießmann

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=53746CF5.4050705@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /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.