public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Include patchwork patch ID in commit message?
Date: Fri, 29 Jan 2016 06:14:49 +0100	[thread overview]
Message-ID: <56AAF549.4020705@denx.de> (raw)
In-Reply-To: <CANr=Z=baZwxjipehP55MxSWF+rUvatT1hmXW8Rn0vhmNPhqyfQ@mail.gmail.com>

Hello Joe,

Am 28.01.2016 um 16:15 schrieb Joe Hershberger:
> Hi Heiko,
>
> On Thu, Jan 28, 2016 at 12:39 AM, Heiko Schocher <hs@denx.de> wrote:
>> Hello Tom,
>>
>> Am 28.01.2016 um 00:45 schrieb Tom Rini:
>>>
>>> On Wed, Jan 27, 2016 at 05:15:17PM -0600, Joe Hershberger wrote:
>>>>
>>>> On Wed, Jan 27, 2016 at 4:22 PM, Tom Rini <trini@konsulko.com> wrote:
>>>>>
>>>>> 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.
>>>>
>>>>
>>>> Would it be more or less compelling if it had a format similar this?
>>>>
>>>> Patchwork: https://patchwork.ozlabs.org/patch/571773/
>>>
>>>
>>> Yes.
>>
>>
>> Sorry, for dummy question ... what should I see in the above link?
>
> The link is the think to see, not what it points to. The idea is that
> instead of just the patch number, include the patch number in a full
> URL for even easier access to the patch.

Uh, ah, got it ... I think the patchworks patchnumber would be enough.
I like Bins proposal, that patchwork add it automatically ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2016-01-29  5:14 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
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 [this message]
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=56AAF549.4020705@denx.de \
    --to=hs@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