All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MX23 patches
Date: Wed, 30 Jan 2013 00:28:22 +0100	[thread overview]
Message-ID: <201301300028.22203.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKp=orr20Gy=GzkJDkkO2BNt=UwFnCoaior5vg0aqH=rdA@mail.gmail.com>

Dear Otavio Salvador,

> On Tue, Jan 29, 2013 at 8:21 PM, Marek Vasut <marex@denx.de> wrote:
> > Hello,
> > 
> > due to the recent influx of patches, I completely lost track of what is
> > going on, what patches need review and what patches are already
> > obsolete. Therefore, I'd like to ask you, Otavio, to proceed as follows:
> > 
> > - I will discard all patches for mx23 currently in my mailbox
> > 
> > - I'd like you to reset the versioning on all your patches and start with
> > clean slate (from V1, as of this moment)
> > - Repost all series you currently have, incl. those you already submitted
> > with proper description in all patches and with a proper cover letter
> > (git NNN -- cover-letter)
> 
> I rolled out, early this morning, the last series (3 series):
> 
> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/152364
> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/152361
> http://article.gmane.org/gmane.comp.boot-loaders.u-boot/152358
> 
> So if you really need me to resend them all, I can do it but those are
> the current versions and previous ones can be ignored.

I wiped all the patches from patchwork now, resubmit everything that is not yet 
applied.

> > - Wait at least one full day (24 hours) between re-sending a series,
> > unless explicitly requested otherwise.
> 
> Ok; deal.
> 
> > - Always CC me, Fabio and Stefano on _all_ the patches in the series, not
> > only selected ones. (you can add "Cc: Us Er <u@s.er>" in the patch
> > description, this will let git send-email automatically handle the Cc)
> 
> I've been trying to follow maintainers role here but I can change it
> and copy you three in all messages. No problem for me.

Just add us on the Cc since we are all directly involved. Obviously, also Cc the 
custodians.

> > - Read [1], esp. the part about In-Reply-To please , apply this only when
> > re- posting series. Do NOT do In-Reply-To for the re-post of the series
> > after this restart, only if V2 is needed from now on.
> 
> One doubt here: when sending v2 I should put the In-Reply-To for v1? I
> read it but it was not clear for me.

Hang the V2 series under the V1 series cover letter. Or resubmit separate 
patches I-R-T.

> Regards,
> 
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Best regards,
Marek Vasut

      reply	other threads:[~2013-01-29 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 22:21 [U-Boot] MX23 patches Marek Vasut
2013-01-29 22:36 ` stefano babic
2013-01-29 22:54 ` Otavio Salvador
2013-01-29 23:28   ` Marek Vasut [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=201301300028.22203.marex@denx.de \
    --to=marex@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 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.