From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Any schedule or plan to publish your "testing" branch?
Date: Thu, 07 Aug 2008 10:52:28 +0200 [thread overview]
Message-ID: <20080807085228.D5B5624848@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 07 Aug 2008 15:27:53 +0800." <1516faed0808070027w4b9e0028j3790de9f8f094177@mail.gmail.com>
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.
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
"Who is the oldest inhabitant of this village?"
"We haven't got one; we had one, but he died three weeks ago."
next prev parent reply other threads:[~2008-08-07 8:52 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 [this message]
2008-08-07 11:50 ` Jerry Van Baren
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=20080807085228.D5B5624848@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