From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Revised custodian git writeup
Date: Wed, 23 Jan 2008 00:32:57 +0100 [thread overview]
Message-ID: <20080122233257.A2EE72430C@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 22 Jan 2008 17:47:10 EST." <4796726E.9030501@ge.com>
In message <4796726E.9030501@ge.com> you wrote:
>
> 1) Master branch is for others to actively base from
others = mostly users aka non-developers
> 2) Master branch is updated just before a pull request
not necessarily only then, but updates should contain code that is
considered to be "good" from the custodian's point of view
> 3) No merge conflicts with the u-boot.git repo when Wolfgang pulls it
Ideally, yes.
> These appear to be contradictory goals. #1 and #2 could be argued to
> not be contradictory, but I'm not buying into that theory. The point of
> people pulling and testing is to find problem, which should be fixed
> *before* a pull request. If the master branch has broken code in it,
Agreed. Please see previous messages. My idea is that the maste
rbranch can be consider as kind of a "stable" branch - it is ahead
compared to the main repo in regards to the the custodian's special
topic, but considered stable. For testing, other branches should be
used (probably with an explicit "-testing" in their name).
> I'm not sure what happens (how git handles it) if patches are applied in
> different orders. What I'm thinking about is if custodians #1 and #2
git has no notation of order or sequence. It is storing content only.
If you apply N independent, non-overlapping patches in arbitray
order, the result will be the same. The individual commits will have
different ID's, but who cares?
> both issue a pull request. Wolfgang pulls #1 and then #2. What happens
> to #2 when he does a merge with the master u-boot.git? Does git insert
> custodian #1 patches ahead of his existing (#2) patches, or do the
> patches end up in a different order in the repos?
It doesn't matter as long as there are no conflicts.
> Then there is the merge conflict, which will be a result of the order
> that Wolfgang pulls from the custodian repos. How does a custodian
> resolve a merge conflict without changing his branch's history?
That's a good point. I have to think about that one...
> (going home to soak my brain in ethanol)
The brain or the liver?
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
"Deliver yesterday, code today, think tomorrow."
next prev parent reply other threads:[~2008-01-22 23:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 1:44 [U-Boot-Users] Revised custodian git writeup gvb.uboot
2008-01-22 7:52 ` Markus Klotzbücher
2008-01-22 8:55 ` Wolfgang Denk
2008-01-22 9:50 ` Haavard Skinnemoen
2008-01-22 13:45 ` Wolfgang Denk
2008-01-22 14:20 ` Haavard Skinnemoen
2008-01-22 14:42 ` Mike Frysinger
2008-01-22 16:34 ` Wolfgang Denk
2008-01-22 18:23 ` Joakim Tjernlund
2008-01-22 18:39 ` Haavard Skinnemoen
2008-01-22 13:50 ` Jerry Van Baren
2008-01-22 14:10 ` Wolfgang Denk
2008-01-22 13:32 ` Jerry Van Baren
2008-01-22 14:03 ` Wolfgang Denk
2008-01-22 14:26 ` Markus Klotzbücher
2008-01-22 16:36 ` Wolfgang Denk
2008-01-22 22:47 ` Jerry Van Baren
2008-01-22 23:32 ` Wolfgang Denk [this message]
2008-01-23 3:15 ` gvb.uboot
2008-01-23 12:04 ` Martin Krause
2008-01-23 12:47 ` Wolfgang Denk
2008-01-23 17:27 ` Martin Krause
2008-01-23 17:30 ` Haavard Skinnemoen
2008-01-22 14:38 ` Haavard Skinnemoen
2008-01-22 14:35 ` Jerry Van Baren
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=20080122233257.A2EE72430C@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