From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Commits missing sign-off from Maintainer/Custodian
Date: Fri, 1 May 2020 14:34:17 -0400 [thread overview]
Message-ID: <20200501183417.GD12564@bill-the-cat> (raw)
In-Reply-To: <CAFOYHZBkFgsec6w-GH8iE8awPVYVWgWCsTdyHEFPqQRy-7Estg@mail.gmail.com>
On Fri, May 01, 2020 at 09:23:18AM +1200, Chris Packham wrote:
> Hi All,
>
> I noticed some recent(ish) commits in u-boot.git are missing a
> sign-off from the maintainer. Is this an omission or an intentional
> change in process?
>
> I don't have a problem either way but if it was an omission I thought
> I'd point it out. If it's intentional then this message can go to
> /dev/null.
One way we differ from the Linux kernel is that it is not common to add
your own S-o-B when applying patches, only when you have to make changes
to them as part of applying.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200501/c93af5aa/attachment.sig>
prev parent reply other threads:[~2020-05-01 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 21:23 Commits missing sign-off from Maintainer/Custodian Chris Packham
2020-05-01 18:34 ` Tom Rini [this message]
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=20200501183417.GD12564@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox