On Wed, Mar 03, 2004 at 09:43:56AM -0500, Larry Jones wrote:
I don't think so -- have you tried it?
Woops, you're right! I knew I'd accomplished it; shame on me for
describing how from (what turned out to be completely fictional
and bogus) memory.
What I *actually* did (and this time I have
On Tue, Mar 02, 2004 at 09:23:43AM -0500, Timothy Stone wrote:
$ cvs -d $REP import -ko -I! -m some meaningful message blojsom
BLOJSOM REL_2_11
Basically, the -ko switch seems to be hosing the JAR files in the
project. Everything gets a Sticky Option of -ko. This kills JARs.
Yup. The -ko
List,
Not necessarily a newcomer to cvs, but I'm experiencing some odd
behavior that is unexpected, at least from within the context of my
experience.
I did a search in the archive, found something close, but not exactly,
in particular how CVS processes wrapper instructions (wrappers, home,
List,
Not necessarily a newcomer to cvs, but I'm experiencing some odd
behavior that is unexpected, at least from within the context of my
experience.
I did a search in the archive, found something close, but not exactly,
in particular how CVS processes wrapper instructions (wrappers, home,
ENV,
Timothy Stone wrote:
My import:
$ cvs -d $REP import -ko -I! -m some meaningful message blojsom
BLOJSOM REL_2_11
Basically, the -ko switch seems to be hosing the JAR files in the
project. Everything gets a Sticky Option of -ko. This kills JARs.
Well, what did you expect? You *told* CVS
Timothy Stone writes:
$ cvs -d $REP import -ko -I! -m some meaningful message blojsom
BLOJSOM REL_2_11
Basically, the -ko switch seems to be hosing the JAR files in the
project. Everything gets a Sticky Option of -ko. This kills JARs.
Yep. An explicit -k option on the command line
