public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] Pull request: u-boot-staging
Date: Thu, 24 Nov 2011 08:57:40 +0200	[thread overview]
Message-ID: <4ECDEAE4.5030100@compulab.co.il> (raw)
In-Reply-To: <20111123201429.AEDF81FFB39E@gemini.denx.de>

Hi,

On 11/23/11 22:14, Wolfgang Denk wrote:
> Dear Andy Fleming,
> 
> In message <CAKWjMd5N1ozpR2O4rWCzPpPzjbZL1xAT0sRhoDz61aSzZSXEyw@mail.gmail.com> you wrote:
>>
>> 13) When to use Acked-by: and Cc:
>>
>> The Signed-off-by: tag indicates that the signer was involved in the
>> development of the patch, or that he/she was in the patch's delivery path.
>>
>> I think that makes the intent of (c) clear.
> 
> Yes, but to me "delivery path" means the path from where the patch has
> been developed through reviewers, other developers that change/improve
> it etc. until it hits it's destination and gets delivered to ...
> well, to where?  In our case to that is the mailing list respective
> PatchWork.  This is where we deliver our patches to.  The delivery
> path ends there.

Is the single patch should be picked manually, from the PatchWork?
If it is, then this is work that custodian does.
Can a custodian pick a patch from the mailing list
(say if PatchWork is down or whatever)?
If yes, then this is also the work that custodian does.

For my understanding, the delivery ends with *unique commit id*
in some repository, which then can get pulled, but has history intact.

Nevertheless, it is a meter of choice, that should be made.
I'm fine with any choice we will make.

-- 
Regards,
Igor.

  reply	other threads:[~2011-11-24  6:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18  8:58 [U-Boot] [GIT PULL] Pull request: u-boot-staging Stefano Babic
2011-11-21 21:10 ` Wolfgang Denk
2011-11-22  5:06   ` Simon Glass
2011-11-22  7:18     ` Stefano Babic
2011-11-22  8:59   ` Stefano Babic
2011-11-22 22:28     ` Wolfgang Denk
     [not found]     ` <4ECC9D3F.2080100@compulab.co.il>
2011-11-23  8:16       ` Stefano Babic
2011-11-23  9:09         ` Igor Grinberg
2011-11-23 16:01           ` Wolfgang Denk
2011-11-23 16:26             ` Igor Grinberg
2011-11-23 16:57               ` Stefano Babic
2011-11-23 17:08                 ` Andy Fleming
2011-11-23 20:14                   ` Wolfgang Denk
2011-11-24  6:57                     ` Igor Grinberg [this message]
2011-11-24 11:51                       ` Wolfgang Denk
2011-11-24 12:15                         ` Igor Grinberg
2011-11-23 20:12                 ` Wolfgang Denk
2011-11-24  6:48                   ` Igor Grinberg
2011-11-24  7:02                     ` Graeme Russ
2011-11-24  7:24                       ` Igor Grinberg
2011-11-24 11:53                       ` Wolfgang Denk
2011-11-24 11:46                     ` Wolfgang Denk
2011-11-24 12:33                       ` Igor Grinberg
2011-11-28 18:52                         ` Wolfgang Denk
2011-11-29  7:34                           ` Igor Grinberg
  -- strict thread matches above, loose matches on Subject: below --
2011-11-23  7:37 Heiko Schocher
2011-11-23 20:26 ` Wolfgang Denk
2011-12-09 13:50 [U-Boot] [GIT PULL] Pull request u-boot-staging Stefano Babic
2011-12-10 21:43 ` Wolfgang Denk

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=4ECDEAE4.5030100@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --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