From: Jon Loeliger <jdl@jdl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot refactoring
Date: Tue, 03 Jul 2007 17:00:52 -0500 [thread overview]
Message-ID: <E1I5qQW-0007cq-3i@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 03 Jul 2007 23:40:03 +0200." <20070703214003.5CEA7353AF8@atlas.denx.de>
So, like, the other day Wolfgang Denk mumbled:
>
> > > 4) Pull Jon's "cmdcfg" patch series into testing.
> >=20
> > Pleas delay this a few days -- there's more brewing still, and
> > it would be best to get the next round completely, I think.
>
> Ummm... I was really on the *verge* of doing this right now. But it's
> your work, so you decide. Does that mean that I should delete these
> patches from my stack ?
>
> 06/11 Jon Loeliger [U-Boot-Users] [PATCH: cmdcfg: 00/19] Introduce initi=
> al versions of n
Actually, if you are up for it now, please do so. It would be good, I think.
But I am slowly working my way through the rest of the include/configs/*.h files
as well. If you are OK with only some of them updated at a time, then we
should go for it. I had sort of assumed you'd like to see all of the config
files updated at approximately the same time. So, if you are willing to do
that step incrementally, go for it!
jdl
next prev parent reply other threads:[~2007-07-03 22:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 18:48 [U-Boot-Users] U-boot refactoring Grant Likely
2007-07-03 21:04 ` Wolfgang Denk
2007-07-03 21:19 ` Jon Loeliger
2007-07-03 21:40 ` Wolfgang Denk
2007-07-03 22:00 ` Jon Loeliger [this message]
2007-07-03 22:44 ` Wolfgang Denk
2007-07-04 18:15 ` Jon Loeliger
2007-07-04 8:20 ` Robert Schwebel
2007-07-04 13:44 ` Wolfgang Denk
2007-07-04 19:11 ` Carsten Schlote
2007-07-05 18:58 ` Jon Loeliger
2007-07-05 20:09 ` Wolfgang Denk
2007-07-05 20:29 ` Jon Loeliger
2007-07-05 23:53 ` Carsten Schlote
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=E1I5qQW-0007cq-3i@jdl.com \
--to=jdl@jdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox