public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull u-boot-mpc83xx.git mpc83xx branch into testing
Date: Mon, 24 Sep 2007 16:47:58 -0600	[thread overview]
Message-ID: <fa686aa40709241547s45c21dfdtda9ecd2894c5b725@mail.gmail.com> (raw)
In-Reply-To: <20070924172628.e334b3ce.kim.phillips@freescale.com>

On 9/24/07, Kim Phillips <kim.phillips@freescale.com> wrote:
> On Mon, 24 Sep 2007 23:52:29 +0200
> Wolfgang Denk <wd@denx.de> wrote:
>
> > In message <20070924161309.9f14b16e.kim.phillips@freescale.com> you wrote:
> > >
> > > > There is no merge window open at the moment.
> > > >
> > > ok, let me understand how you want this to work.
> > >
> > > my original intent was for you to pull 837x support into your /testing/
> > > tree so that gcl's mass-rename scripts could do their magic on the 837x
> > > board port too.
> >
> > No, that will not work. You would move Grant's base under his feet.
>
> this goes both ways.  True, Grant's work is more intrusive, but that
> just means that all work that is or can be affected by it be staged in
> a single common tree.  My understanding is you have designated the
> -testing tree for this particular purpose.

I don't think that's quite true.  In the last merge window, -testing
got used to stage changes for the merge window with the least possible
impact.  In that case, it was Jon's CMD_* changes which needed to go
in first.

It makes total sense to stage changes in the custodian trees, but
Wolfgang retains the right to decide what order those changes get
staged into -testing, and also to request custodians to
merge/rebase/retest before pulling their tree.

>
> > > but it sounds like you want me to hold on to new 83xx boards/features
> > > until you make a final (non-rc) release?  Sounds like I should be
> > > asking gcl to share his scripts then.
> >
> > No again. Please just wait until we have a somehwat  stable  base  in
> > testing,  and Grant has applied his patches there. Then use *this* as
> > base for any new submissions, which you then should post in the merge
> > window.
>
> It sounds like you're suggesting everyone halt all new development
> indefinitely.  Please clarify.

Not at all!  It is not a suggestion to halt development; but it is a
warning that custodians need to do either a rebase or a merge before
it is pulled when the window opens (or before Wolfgang chooses to pull
them into -testing).

Besides; if I come up with a set of changes that will make a merge or
rebase absolutely impossible, I'm sure Wolfgang will tell me what I
can do with my patchset.  :-)

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-09-24 22:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 20:19 [U-Boot-Users] Please pull u-boot-mpc83xx.git mpc83xx branch into testing Kim Phillips
2007-09-24 20:25 ` Grant Likely
2007-09-24 20:39 ` Wolfgang Denk
2007-09-24 21:13   ` Kim Phillips
2007-09-24 21:46     ` Grant Likely
2007-09-24 21:52     ` Wolfgang Denk
2007-09-24 22:26       ` Kim Phillips
2007-09-24 22:47         ` Grant Likely [this message]
2007-09-25 15:02           ` Kim Phillips
2007-09-25 15:24             ` Grant Likely
2007-09-25 22:37     ` Wolfgang Denk
2007-11-19  3:01 ` [U-Boot-Users] Please pull u-boot-mpc83xx.git mpc83xx branch intotesting Liu Dave
2007-11-19  6:57   ` Grant Likely
2007-11-19  7:17     ` Liu Dave
2007-11-19  7:43       ` Stefan Roese
2007-11-19 17:25         ` Kim Phillips
2007-11-19 20:58           ` 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=fa686aa40709241547s45c21dfdtda9ecd2894c5b725@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --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