From: Andrew Wozniak <awozniak@mc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot source - cvs versus git
Date: Thu, 17 Nov 2005 08:55:24 -0500 [thread overview]
Message-ID: <437C8BCC.4010100@mc.com> (raw)
In-Reply-To: <20051116234203.5BA68352568@atlas.denx.de>
Wolfgang Denk wrote:
> In message <437BBA6A.7080708@mc.com> you wrote:
>> I understand that U-Boot development and source is now management using
>> "git". Since the cvs tree does seem to be pretty recent, is it ok to
>
> The git and CVS trees are 100% in sync. All commits on the git tree
> have been checked in in parallel on the CVS tree, too.
This is good news.
> Perhaps you might be so kind as to elucidate why you think the CVS
> tree might not be up to date?
I recall reading a few older messages which suggested that CVS tree
might be lagging behind.
>> pull the latest U-Boot source from the cvs tree? Or is there less risk
>> of missing important code patches by using git?
>
> The code is exactly the same.
>
>> After several failures at building git for my RH7.2 system, I decided to
>> go back to using cvs - it just works!
>
> Ummm.. RH7.2 is pretty old, with a list of known andunfixed exploits.
> If I were you I would consider to update my development host system
> insted.
Yes it is outdated. This is a "crash-and-burn" machine I had been using
for testing legacy products and haven't had time to upgrade it.
Considering it is a triple boot machine makes upgrading even more time
consuming.
Guten tag, Andrew
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2005-11-17 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 23:02 [U-Boot-Users] u-boot source - cvs versus git Andrew Wozniak
2005-11-16 23:42 ` Wolfgang Denk
2005-11-17 13:55 ` Andrew Wozniak [this message]
2005-11-17 15:05 ` Wolfgang Denk
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=437C8BCC.4010100@mc.com \
--to=awozniak@mc.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.