From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Include patchwork patch ID in commit message?
Date: Wed, 27 Jan 2016 17:22:09 -0500 [thread overview]
Message-ID: <20160127222209.GS426@bill-the-cat> (raw)
In-Reply-To: <CANr=Z=YPLfukiUsPgbfdvAjmznzewzTZbm=_xhNxDHRmcLnP-g@mail.gmail.com>
On Wed, Jan 27, 2016 at 03:08:09PM -0600, Joe Hershberger wrote:
> Hi Tom,
>
> I'm playing with the idea of including the patchwork patch ID in the
> commit message of each commit that I apply to provide better
> cross-reference ability.
>
> * Access to comments on patches
> * Clarity on exactly which version of a patch was applied
> * No need to search by patch subject
>
> Here is an example in a working branch:
>
> http://git.denx.de/?p=u-boot/u-boot-net.git;a=commit;h=48f9a0c786d0a3cbfdf45846567deaebe27a334a
I'd prfer Patchwork or Patchwork-ID or something not just Patch.
>
> What do you (or anyone else) think?
Well, I'm not a super fan of it. For your second point, this is why I
use bundles, mutt and a macro. For the other points, at least I find
google does a good job pulling up the right patch at least.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160127/e72d31c6/attachment.sig>
next prev parent reply other threads:[~2016-01-27 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:08 [U-Boot] Include patchwork patch ID in commit message? Joe Hershberger
2016-01-27 22:22 ` Tom Rini [this message]
2016-01-27 23:15 ` Joe Hershberger
2016-01-27 23:45 ` Tom Rini
2016-01-28 0:05 ` Joe Hershberger
2016-01-28 1:30 ` Tom Rini
2016-01-28 1:49 ` Bin Meng
2016-01-28 6:49 ` Heiko Schocher
2016-01-28 15:40 ` Tom Rini
2016-01-28 15:19 ` Joe Hershberger
2016-01-28 6:39 ` Heiko Schocher
2016-01-28 15:15 ` Joe Hershberger
2016-01-29 5:14 ` Heiko Schocher
2016-01-29 9:57 ` Masahiro Yamada
2016-01-31 15:59 ` Albert ARIBAUD
2016-01-28 15:45 ` Tom Rini
2016-01-28 6:13 ` Heiko Schocher
2016-01-28 15:16 ` Joe Hershberger
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=20160127222209.GS426@bill-the-cat \
--to=trini@konsulko.com \
--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.