From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Any schedule or plan to publish your "testing" branch?
Date: Thu, 07 Aug 2008 07:50:01 -0400 [thread overview]
Message-ID: <489AE169.2050604@ge.com> (raw)
In-Reply-To: <20080807085228.D5B5624848@gemini.denx.de>
Wolfgang Denk wrote:
> In message <1516faed0808070027w4b9e0028j3790de9f8f094177@mail.gmail.com> you wrote:
>> Yes, William hit the point. Actually It seems my work is based on two
>> different custodian trees, for example, Scott's NAND tree and
>> u-boot-at91 tree. If the 2 two trees do not merge each other,
>> sometimes I got screwed. I guess `git ' may help at this situation,
>> but I don't know how. :-) I just wanted to know the status of the
>> NAND tree. Maybe I did not express myself clearly in the last email.
>
> You can create your own local development branch, and merge both the
> NAND testing branch and the at91 stuff into this branch. There may be
> merge conflicts, of course, but I think both trees are pretty
> orthogonal to each other, so chances for such conflicts are probably
> small.
...and if there *are* merge conflicts, you can contribute back to the
u-boot list (a) that there is a pending conflict and (b) a resolution,
if you have one. Having the knowledge of a merge conflict *before* the
merge window opens is useful. Having a proposed resolution is even more
useful.
Thanks,
gvb
next prev parent reply other threads:[~2008-08-07 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 1:02 [U-Boot-Users] Any schedule or plan to publish your "testing" branch? Hong Xu
2008-08-07 5:34 ` Wolfgang Denk
2008-08-07 7:02 ` William Juul
2008-08-07 7:27 ` Hong Xu
2008-08-07 8:52 ` Wolfgang Denk
2008-08-07 11:50 ` Jerry Van Baren [this message]
2008-08-07 14:10 ` Scott Wood
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=489AE169.2050604@ge.com \
--to=gerald.vanbaren@ge.com \
--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.