From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Switching SCM to git and commit/review policy
Date: Fri, 13 Jun 2008 15:38:23 -0300 [thread overview]
Message-ID: <87od65rxi8.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <g2ubb9$a55$1@ger.gmane.org> (Koen Kooi's message of "Fri\, 13 Jun 2008 19\:38\:50 +0200")
Koen Kooi <k.kooi@student.utwente.nl> writes:
> pHilipp Zabel wrote:
>
>>>> Personally, I'd like to see every patch to OE being sent to and
>>>> reviewed on the mailing list.
>>> I'd like to see that every commit has at least 2 SOBs, I care less on how
>>> they get there. Having the review out in the open should be the end goal,
>>> though.
>>
>> From Documentation/SubmittingPatches:
>> "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."
>>
>> In the kernel Signed-off-by is primarily used to mark the way a patch
>> took into the kernel. If we do this, maybe we should use the same
>> nomenclature and have Acked-by for statements of approval. (And
>> eventually Tested-by/Reviewed-by, too?)
>
> That is probably a good idea.
I don't know how kernel people do to amend the patch to add the
acked-by/whatever data into each patch. It can be a big amount of work
to do an iteractive rebase for every ack given on ml for each patch
and with a high risk of human mistake while doing it.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2008-06-13 18:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 8:20 Switching SCM to git and commit/review policy Richard Purdie
2008-06-13 10:06 ` pHilipp Zabel
2008-06-13 12:43 ` Cliff Brake
2008-06-13 14:16 ` Koen Kooi
2008-06-16 16:35 ` Rolf Leggewie
2008-06-13 17:17 ` Otavio Salvador
2008-06-13 17:49 ` Tom Rini
2008-06-13 14:09 ` Koen Kooi
2008-06-13 16:25 ` pHilipp Zabel
2008-06-13 17:38 ` Koen Kooi
2008-06-13 18:38 ` Otavio Salvador [this message]
2008-06-13 19:37 ` Holger Freyther
2008-06-13 21:00 ` Otavio Salvador
2008-06-16 11:10 ` Rolf Leggewie
2008-06-16 13:16 ` Otavio Salvador
2008-06-16 14:30 ` Rolf Leggewie
2008-06-16 15:48 ` Otavio Salvador
2008-06-16 16:27 ` Rolf Leggewie
2008-06-16 17:03 ` Otavio Salvador
2008-06-16 14:17 ` Rolf Leggewie
2008-06-16 22:42 ` Florian Boor
2008-06-16 23:21 ` Michael 'Mickey' Lauer
2008-06-16 13:09 ` Mark Brown
2008-06-17 9:51 ` Jan Lübbe
2008-06-24 9:57 ` Graeme Gregory
2008-06-24 14:01 ` Alain M.
2008-06-24 18:48 ` Leon Woestenberg
2008-06-24 20:13 ` Philip Balister
2008-06-24 18:33 ` Koen Kooi
2008-06-24 19:06 ` Tom Rini
2008-06-24 20:51 ` Florian Boor
2008-06-24 21:29 ` Tom Rini
2008-06-24 22:51 ` Leon Woestenberg
2008-06-25 1:22 ` Luís Vitório Cargnini
2008-07-14 12:22 ` Rolf Leggewie
2008-07-14 18:57 ` Koen Kooi
2008-07-14 23:24 ` Core team (was: Switching SCM to git and commit/review policy) Rolf Leggewie
2008-07-14 23:24 ` Rolf Leggewie
2008-07-15 9:45 ` Richard Purdie
2008-07-18 18:30 ` Shane Volpe
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=87od65rxi8.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.