public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Formal acks and patchwork
Date: Mon, 23 May 2011 21:19:29 +0200	[thread overview]
Message-ID: <4DDAB341.20006@aribaud.net> (raw)
In-Reply-To: <20110523184447.C3A941499BF9@gemini.denx.de>

Le 23/05/2011 20:44, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4DDA69A1.1070009@aribaud.net>  you wrote:
>>
>>> Note that this is NOT nitpicking:  Patchwork will automatically add
>>> such correct Acked-by: lines to the patch, so we don't have to track
>>> thse manually - this saves a LOT of time to the maintainers.
>>
>> One question: where is the information presented in patchwork, apart
>> from coloring the ack line when displaying the patch discussion thread?
>> I cannot find e.g. a summary list of all acks to a given patch.
>
> PW automatically inserts this into the patch if you click on the
> "Download: mbox" link, or is you access the patch through pwclient.
>
> For example, instead of applying a patch directly from my mailbox I
> use this file only to get the hash value for the PW entry, and then
> use pwclient to apply it and to update it's state:
>
>          HASH=$(pwparser.py --hash<$PATCH)
>          if [ -z "$HASH" ]
>          then
>                  echo "ERROR: $PATCH - no such entry in PatchWork">&2
>                  exit 1
>          fi
>
>          if pwclient apply -h $HASH
>          then
>                  pwclient update -s 'Accepted' -h $HASH
>          fi
>
> This is extremely convenient as it automatically takes care of both
> the Acks and the state change.

Thanks. Looks like this could be handy for many others. Maybe it should 
be 'backported' into pwclient itself as a new command.

> Best regards,
>
> Wolfgang Denk

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-05-23 19:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 11:54 [U-Boot] [PATCH] [Timer]Remove calls to [get, reset]_timer outside arch/ Graeme Russ
2011-05-23 12:19 ` Scott McNutt
2011-05-23 12:32   ` Graeme Russ
2011-05-23 13:12     ` Scott McNutt
     [not found]       ` <4DDA9CDA.1080401@comcast.net>
     [not found]         ` <4DDAA77F.7020708@psyent.com>
2011-05-23 20:10           ` Graeme Russ
2011-05-23 20:49             ` J. William Campbell
2011-05-23 21:02               ` Graeme Russ
2011-05-23 21:15                 ` J. William Campbell
2011-05-24  5:13                 ` Graeme Russ
2011-05-24 15:41                   ` J. William Campbell
2011-05-23 21:53               ` Wolfgang Denk
2011-05-23 22:44                 ` Graeme Russ
2011-05-24  3:20                   ` Mike Frysinger
2011-05-23 12:31 ` Jens Scharsig
2011-05-23 13:22   ` Wolfgang Denk
2011-05-23 14:05     ` [U-Boot] Formal acks and patchwork (was: [PATCH] [Timer]Remove calls to [get, reset]_timer outside arch/) Albert ARIBAUD
2011-05-23 18:44       ` Wolfgang Denk
2011-05-23 19:19         ` Albert ARIBAUD [this message]
2011-05-23 19:42           ` [U-Boot] Formal acks and patchwork Wolfgang Denk
2011-05-23 20:15             ` Albert ARIBAUD
2011-05-23 13:34 ` [U-Boot] [PATCH] [Timer]Remove calls to [get, reset]_timer outside arch/ Jens Scharsig
     [not found] ` <BANLkTik3W7WJbRuiKsC8m0f8iof7JL-ZMg@mail.gmail.com>
2011-05-23 20:09   ` Graeme Russ
2011-05-24 10:54 ` Graeme Russ
2011-05-24 11:13   ` Graeme Russ
2011-05-25 12:17   ` Graeme Russ

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=4DDAB341.20006@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox