From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM Workflow: rebase on ARM repositories
Date: Mon, 03 Sep 2012 21:06:43 +0200 [thread overview]
Message-ID: <20120903190643.3B994203EDC@gemini.denx.de> (raw)
In-Reply-To: <5044A44F.2050204@denx.de>
Dear Stefano,
In message <5044A44F.2050204@denx.de> you wrote:
>
> One of them uses u-boot-imx for his development, and of course after I
> rebased my tree he got into trouble, due to using a commit that does not
> exist anymore.
Thanks for bringing up this topic.
> Albert has described the way we are currently using in
> http://www.denx.de/wiki/view/U-Boot/CustodianGitTrees. I think you konow
> very well and it is the way we follow, and we usually rebase our tree
> after u-boot-arm is merged by Wolgang in mainline. I want to discuss
> here if we really need it and if this is the correct way to do.
I think it is wrong to rebase any tree for which it is not very
clearly and lodly announced that this tree gets rebased on a more or
less regular base. linux-next is such an example - we allknow it gets
rebased frequently, so we can arrange with it (though I have to admit
that I dn't like it, and that I've been bitten myself more than once
by this).
For u-boot-*, most users I know are not aware of any rebasing policy.
> My big question is if we should not to come back using "git pull" to
> downstream mainline from Wolfgang's tree, instead of continuos rebase. I
> know that we switched to rebase to avoid a lot of "git merge commits",
> but maybe this is not so bad as rebasing.
I would prefer to have at least rebase-free "master" branches in all
custodian repositories. It is perfectly OK to have working branches,
and to rebase these as work progresses. But for the master branches,
a rebase should be more or less tabu.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
We are Microsoft. Unix is irrelevant. Openness is futile. Prepare to
be assimilated.
prev parent reply other threads:[~2012-09-03 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 12:36 [U-Boot] ARM Workflow: rebase on ARM repositories Stefano Babic
2012-09-03 13:13 ` Stefan Roese
2012-09-03 14:15 ` Stefano Babic
2012-09-03 18:02 ` Albert ARIBAUD
2012-09-03 19:13 ` Wolfgang Denk
2012-09-03 19:47 ` Albert ARIBAUD
2012-09-03 20:52 ` Wolfgang Denk
2012-09-04 9:37 ` Stefano Babic
2012-09-04 12:45 ` Albert ARIBAUD
2012-09-04 15:32 ` Stephen Warren
2012-09-03 19:06 ` Wolfgang Denk [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=20120903190643.3B994203EDC@gemini.denx.de \
--to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox