From: Kent Borg <kentborg@borg.org>
To: Andrew Johnson <anj@aps.anl.gov>
Cc: Tom Rini <trini@kernel.crashing.org>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: BK to CVS?
Date: Fri, 5 Oct 2001 12:23:40 -0400 [thread overview]
Message-ID: <20011005122340.E8157@borg.org> (raw)
In-Reply-To: <3BBDD64F.97B0057B@aps.anl.gov>; from anj@aps.anl.gov on Fri, Oct 05, 2001 at 10:48:31AM -0500
On Fri, Oct 05, 2001 at 10:48:31AM -0500, Andrew Johnson wrote:
> Why don't you use the cvs vendor branch to do most of the work for you,
> rather than generating deltas yourself?
And so do complete exports? I didn't start out that way because I am
running BK on an underpowered machine and complete exports are slow.
Aso, where I work there are stupid security policies that force me to
mail between that real internet connection that can do BK and the
broken corporate network, and mailing whole kernels seems fraught with
problems.
Your suggestion seesm to imply that complete exports are more reliable
than deltas. True?
Thanks,
-kb, the Kent who is close to conclusion, if for no other reason,
because he has to get some real work done.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-05 16:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 17:05 BK to CVS? Kent Borg
2001-10-03 18:32 ` Tom Rini
2001-10-04 13:25 ` Kent Borg
2001-10-04 20:29 ` Tom Rini
2001-10-05 15:11 ` Kent Borg
2001-10-05 15:48 ` Andrew Johnson
2001-10-05 16:04 ` Ricardo Scop
2001-10-06 2:25 ` Dan Malek
2001-10-05 20:52 ` BK to CVS? + MDIO Ricardo Scop
2001-10-06 3:34 ` Tom Rini
2001-10-06 3:42 ` Re[2]: " Ricardo Scop
2001-10-06 3:41 ` Dan Malek
2001-10-08 12:01 ` Jerry Van Baren
2001-10-08 13:06 ` Wolfgang Denk
2001-10-06 2:43 ` BK to CVS? Tom Rini
2001-10-05 16:23 ` Kent Borg [this message]
2001-10-05 16:42 ` Andrew Johnson
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=20011005122340.E8157@borg.org \
--to=kentborg@borg.org \
--cc=anj@aps.anl.gov \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/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;
as well as URLs for NNTP newsgroup(s).