All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jluebbe@lasnet.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Switching SCM to git and commit/review policy
Date: Tue, 17 Jun 2008 11:51:13 +0200	[thread overview]
Message-ID: <1213696273.28438.50.camel@localhost> (raw)
In-Reply-To: <20080616130932.GA22229@sirena.org.uk>

On Mon, 2008-06-16 at 14:09 +0100, Mark Brown wrote:
> On Fri, Jun 13, 2008 at 03:38:23PM -0300, Otavio Salvador wrote:
> 
> > 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.
> 
> For the most part everything except the Signed-off-by is added by the
> patch submitter as they submit and resubmit the patch - often that
> information will just get dropped on the floor otherwise.

Instead of having the "acked-by" in the changeset, we could have it
implicit in the history:

* Everyone with commit access has their own branch
  - org.openembedded.dev.<username>
* Someone else reviewes/compiletestes the changes and then merges the 
  branch into .dev
  - The name of the reviewer then appears in the merge

Trivial changes might go into .dev directly...

-- 
Jan Lübbe <jluebbe@lasnet.de>            http://sicherheitsschwankung.de
 gpg-key      1024D/D8480F2E 2002-03-20
 fingerprint  1B25 F91F 9E7B 5D4F 1282  02D6 8A83 8BE4 D848 0F2E




  reply	other threads:[~2008-06-17  9:52 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
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 [this message]
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=1213696273.28438.50.camel@localhost \
    --to=jluebbe@lasnet.de \
    --cc=openembedded-devel@lists.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.