From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Pull request u-boot-mpc85xx.git
Date: Mon, 02 May 2011 19:05:42 +0200 [thread overview]
Message-ID: <20110502170542.D65B5151F84@gemini.denx.de> (raw)
In-Reply-To: <BANLkTimz0ifsCmF9oo-Q_9Sv9wC0rQtMQQ@mail.gmail.com>
Dear Tabi Timur-B04825,
In message <BANLkTimz0ifsCmF9oo-Q_9Sv9wC0rQtMQQ@mail.gmail.com> you wrote:
>
> How? Patchwork uses the same subject line as the email. There's
> still the problem of trying to correlate the actual commit to the
> entry in patchwork.
>
> On the other hand, I don't know of any good way to correct a patch's
> subject line without having the patch re-submitted to the mailing
> list.
It's possible to match a patch based on it's content.
For example, you can use something like
HASH=$(/home/wd/bin/pwparser.py --hash <$MBOX)
pwclient apply -h $HASH
pwclient update -s 'Accepted' -h $HASH
[error checking omitted here]
to apply and update the status of a patch in PW. So you can of course
find out which patch it was based on the hash, which depends on the
content, not the subject.
But this is way too expensive and time consuming for regular work.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Q: Why do mountain climbers rope themselves together?
A: To prevent the sensible ones from going home.
next prev parent reply other threads:[~2011-05-02 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 20:45 [U-Boot] [GIT PULL] Pull request u-boot-mpc85xx.git Kumar Gala
2011-04-30 21:03 ` Wolfgang Denk
2011-05-02 15:00 ` Kumar Gala
2011-05-02 15:42 ` Tabi Timur-B04825
2011-05-02 17:05 ` Wolfgang Denk [this message]
2011-05-02 17:06 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2011-04-29 12:57 Kumar Gala
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=20110502170542.D65B5151F84@gemini.denx.de \
--to=wd@denx.de \
--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