From: Andrew Johnson <anj@aps.anl.gov>
To: Kent Borg <kentborg@borg.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: BK to CVS?
Date: Fri, 05 Oct 2001 11:42:14 -0500 [thread overview]
Message-ID: <3BBDE2E6.B65B3925@aps.anl.gov> (raw)
In-Reply-To: 20011005122340.E8157@borg.org
Kent Borg wrote:
>
> 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.
Can't you persuade your security people to allow you to make an incoming
ssh connection to your repository machine from your BK machine? If so
then you shouldn't need to use mail, but if not then your idea of mailing
patches might be better if you can get it to work. On the BK side you
probably don't have to do a complete export every day, just an update (or
whatever the BK equivalent is, I only know CVS...) and then you do a cvs
import of that tree.
> Your suggestion seesm to imply that complete exports are more reliable
> than deltas. True?
If that's a question about BK I can't answer it as I've never used BK, so
don't make that implication. I didn't really look at precisely what
you're doing with the BK stuff (because I don't understand the
terminology), I just thought about what you're trying to accomplish, which
is basically what cvs import does.
Sorry if that was a wild goose chase...
- Andrew
--
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-10-05 16:42 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
2001-10-05 16:42 ` Andrew Johnson [this message]
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=3BBDE2E6.B65B3925@aps.anl.gov \
--to=anj@aps.anl.gov \
--cc=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.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).