5. If you are using CTM to receive the "*,v" files and then using
the "cvs" command to check out your source tree, then I don't know
whether you need to delete your ",v" files and replace them or not.
You do need to delete your ,v files in this case (only for the crypto
dirs).
M
--
Mark
In article [EMAIL PROTECTED],
Sheldon Hearn [EMAIL PROTECTED] wrote:
Warner, Mark says that this applies if you used CTM to get cvs's ,v
files, not CTM. Also, he clarified the last sentence for me, by saying
that it's the crypto ,v files that need to be removed and not the
checked out
In article [EMAIL PROTECTED],
Udo Erdelhoff [EMAIL PROTECTED] wrote:
What about the non-US cvsup mirrors?
Mirror sites don't have a problem, and they shouldn't do anything
special.
John
--
John Polstra [EMAIL PROTECTED]
John D. Polstra
On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote:
2711:
If you used to get your crypto files from internat, AND you
used cvsup to get cvs' ,v files, then the latest changes
to the source collections will impact you. You will need to
remove all the crypto
On Fri, 14 Jul 2000, Sheldon Hearn wrote:
:
:
:On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote:
:
: 2711:
: If you used to get your crypto files from internat, AND you
: used cvsup to get cvs' ,v files, then the latest changes
: to the source collections will impact you.
On Fri, 14 Jul 2000 07:36:38 EST, David Scheidt wrote:
:Warner, Mark says that this applies if you used CTM to get cvs's ,v
:files, not CTM. Also, he clarified the last sentence for me, by saying
Should this read "used CTM ... not CVS" or "used CVS ... not CTM"?
Argh, what is it about
How can I tell if I need to nuke my crypto files? Sounds like I should
have this problem but it doen't look like I do. I looked through the
commits for the past few days searching for crypto, and I have all of the
files that were commited. (secure/lib/libcrypto/Makefile Makefile.inc from
On Fri, Jul 14, 2000 at 01:56:31PM +0200, Sheldon Hearn wrote:
Also, he clarified the last sentence for me, by saying that it's the
crypto ,v files that need to be removed and not the checked out crypto
files.
What about the non-US cvsup mirrors? Most of them used cvsup to mirror
the crypto
On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote:
2711:
If you used to get your crypto files from internat, AND you
used cvsup to get cvs' ,v files, then the latest changes
to the source collections will impact you. You will need to
remove all the crypto
cd /usr/src/whereever cvs diff
or just check your ``cvs checkout'' output for lines beginning with M.
How can I tell if I need to nuke my crypto files? Sounds like I should
have this problem but it doen't look like I do. I looked through the
commits for the past few days searching for
In message [EMAIL PROTECTED] John Polstra writes:
: This is probably a candidate for UPDATING.
:
: That wouldn't hurt. But it actually affects _all_ branches, I
: believe. So in a way, UPDATING doesn't cover enough ground.
Does anybody have any text that is better than the following?
"Warner" == Warner Losh [EMAIL PROTECTED] writes:
Warner In message [EMAIL PROTECTED] John Polstra writes:
Warner : This is probably a candidate for UPDATING.
Warner :
Warner : That wouldn't hurt. But it actually affects _all_ branches, I
Warner : believe. So in a way,
In message [EMAIL PROTECTED] Martin Hopkins
writes:
: "Warner" == Warner Losh [EMAIL PROTECTED] writes:
:
: Warner In message [EMAIL PROTECTED] John Polstra
:writes:
: Warner : This is probably a candidate for UPDATING.
: Warner :
: Warner : That wouldn't hurt. But it
In message [EMAIL PROTECTED] John Polstra writes:
: This is probably a candidate for UPDATING.
:
: That wouldn't hurt. But it actually affects _all_ branches, I
: believe. So in a way, UPDATING doesn't cover enough ground.
Does anybody have any text that is better than the following?
Warner In message [EMAIL PROTECTED] Martin
Hopkins writes:
Warner : "Warner" == Warner Losh [EMAIL PROTECTED] writes:
Warner :
Warner : Warner In message [EMAIL PROTECTED] John
Polstra writes:
Warner : Warner : This is probably a candidate for UPDATING.
"Mark" == Mark Murray [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] John Polstra writes:
: This is probably a candidate for UPDATING.
:
: That wouldn't hurt. But it actually affects _all_ branches, I
: believe. So in a way, UPDATING doesn't cover enough
"Mark" == Mark Murray [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] John Polstra writes:
: This is probably a candidate for UPDATING.
:
: That wouldn't hurt. But it actually affects _all_ branches, I
: believe. So in a way, UPDATING doesn't cover
I haven't looked into it too deeply yet because of other source tree
problems, but if you used to get your crypto ,v files from internat,
you will suffer some funny problems unless you nuke the old checked-out
files.
My apologies if this is old news, but I see nothing in UPDATING.
The
My apologies if this is old news, but I see nothing in UPDATING.
I sent it to ctm-announce...
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In article [EMAIL PROTECTED],
Brian Somers [EMAIL PROTECTED] wrote:
I haven't looked into it too deeply yet because of other source tree
problems, but if you used to get your crypto ,v files from internat,
you will suffer some funny problems unless you nuke the old checked-out
files.
20 matches
Mail list logo
