Liquidchild writes:
When i run the cvs export command either through WinCVS or on the
command line using
[...]
it exports the ecc module with the CVSROOT folders and CVS folders.
Have you looked at the repository to see if someone managed to actually
add those directories to it?
-Larry
When i run the cvs export command either through WinCVS or on the
command line using
cvs export -r DNOW ecc
it exports the ecc module with the CVSROOT folders and CVS folders.
Can anyone give me a hint, or preferably the answer as to what I am
doing wrong!
Thanks in advance guys
S
in the sandbox/export.
Here is what I envision (from the description above) jacinleyoung did :
cvs checkout modA
cd modA
cvs tag tag123
cd ..
cvs export -r tag123 modB
#results in empty directories created in modB, which is the current
EXPECTED
result.
In which case I could support (someone else's
[EMAIL PROTECTED] wrote:
Hi all
I think the situation is
There are two module
modA
modB
if I tag modA with 'tag123'
then I export modB with 'tag123',
it will return the directories of modB but not the files
Is this a bug?
Jacinle
Hint, You are seeing the effects that are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Hi all
I think the situation is
There are two module
modA modB
if I tag modA with 'tag123' then I export modB with 'tag123', it
will return the directories of modB but not the files Is this a
bug?
It's not the
envision (from the description above) jacinleyoung did :
cvs checkout modA
cd modA
cvs tag tag123
cd ..
cvs export -r tag123 modB
#results in empty directories created in modB, which is the current EXPECTED
result.
In which case I could support (someone else's patch) to do (B), however (A)
is a non
Hi all
I think the situation is
There are two module
modA
modB
if I tag modA with 'tag123'
then I export modB with 'tag123',
it will return the directories of modB but not the files
Is this a bug?
Jacinle
___
Info-cvs mailing list
[EMAIL PROTECTED]
Hi
I have tagged the project with tag 20041213
But in export it show
cvs export -r 20041213
cvs export: Updating deploy
But no files are exported!
But a non exist tag will show error
cvs export -r abc deploy
cvs [export aborted]: no such tag abc
This kind of things are always happening
)
Now I want to export this module, but just the part tagged like mentioned
above.
(cvs export -r AmpersandModule_Version_1 ModuleMain)
I always get the error:
cvs export: could not read RCS file for AmpersandModule
cvs [export aborted]: no such tag AmpersandModule_Version_1
CVS Version:
Concurrent
Please excuse me, and replace checkout with export below. I was talking about
cvs export the whole time.
At 10:00 am 20/2/04, Andy Jones wrote:
I thought I could use cvs -n export to show a list of files with a certain tag.
But I got this instead:
$ cvs -n export -r rel_ta-2-3-2_040204
\testing
using export command on dos prompt as
c:\cvs export -D 11/02/03 -d e:\temp testing
it gives me an error as below
cvs export: No CVSROOT specified! Please use the `-d' option
cvs [export aborted]: or set the CVSROOT environment variable.
I have even used the -d option
\testing
Now when i want to export data from
e:\cvs\repository\testing
to
e:\temp\testing
using export command on dos prompt as
c:\cvs export -D 11/02/03 -d e:\temp testing
it gives me an error as below
cvs export: No CVSROOT specified! Please use the `-d
Hi
As for checking out with different line endings: I haven't tried this but you
could use a windows cvs.exe and run it with wine on *ix, that may give
you DOS-endings even on *ix.
bye Fabi
___
Info-cvs mailing list
[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maarten de Boer wrote:
|Well, but isn't export ment to do this: a special checkout of your
|module destined to be given to third parties. those third parties do not
|necesarily use the same platform as you, when you do the export... And
|using a dos
Hello,
We do centralized tarball and zip-file generation for our project, and
we use cvs export for this. The problem is that, since we run this on
a GNU/Linux box, the files that get included in the zip all have
unix-style end-of-lines. Is there a way to force cvs export to do
end-of-line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maarten de Boer [EMAIL PROTECTED] writes:
We do centralized tarball and zip-file generation for our project, and
we use cvs export for this. The problem is that, since we run this on
a GNU/Linux box, the files that get included in the zip all have
Maarten de Boer writes:
Is there a way to force cvs export to do
end-of-line translation for a specific target?
No. The CVS philosophy is that you should run the CVS command on the
platform where you want the files.
-Larry Jones
I've got more brains than I know what to do with. -- Calvin
I suppose you could also use something like this:
cvs -d host:/repository/path rlog module |\
egrep '^(RCS file|keyword substitution):' |\
sed -e 's/,v//' -e 's,/repository/path/,,'
and then look for 'keyword substituion: kb' and know that the RCS file
given above is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maarten de Boer [EMAIL PROTECTED] writes:
I would say that this kind of use of cvs export is nothing out of the
ordinary...
I do not agree as this kind of use violates the principle of least
astonishment.
Well, but isn't export ment
Hi,
I have just discovered what may be a bug in cvs,
but could not find any reference to it in any
discussion groups or web.
OS: SuSe Linux 8.0
cvs version: 1.11.1p1 on cvs server
1.11.1p1 on client1
1.11.6 on client2
I have some files checked out (with cvs
Hi,
I have just discovered what may be a bug in cvs,
but could not find any reference to it in any
discussion groups or web.
OS: SuSe Linux 8.0
cvs version: 1.11.1p1 on cvs server
1.11.1p1 on client1
1.11.6 on client2
I have some files checked out (with cvs
Folks,
!--
export 1
--
cvs -z9 -q export -l -r V2-03[build-217] -d ./rel
test/incremental/V2-03/bug1234.sql
!--
output 1 (expected)
--
U ./rel/bug1234.sql
!--
export 2
--
cvs -z9 -q export -l -r V2-03[build-217] -d ./rel
test/incremental/V2-03/bug1234.sql test/incremental/V2-03/bug2467.sql
Chris Chang writes:
!--
actual output 2 (_not_ expected)
--
U ./rel/test/incremental/V2-03/bug1234.sql
U ./rel/test/incremental/V2-03/bug2467.sql
!--
expected output 2
--
U ./rel/bug1234.sql
U ./rel/bug2467.sql
Any idea?
When you checkout/export a single module/directory/file
Hello,
exporting part of a repository with
cvs -d :fork:/repository export -Dnow module/submodule
fails (same with :ext:) with server message
cvs [export aborted]: cannot export into a working directory
but
cvs -d :local:/repository export -Dnow module/submodule
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] (John Minnihan) wrote:
In all the years I've used CVS, I've institutionalized use of 'cvs
export' only briefly at one client. And that was only to satisfy some
nimrod (who didn't understand cvs) who screamed - repeatedly - get rid
[EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] (John Minnihan) wrote:
In all the years I've used CVS, I've institutionalized use of 'cvs
export' only briefly at one client. And that was only to satisfy some
nimrod (who didn't understand cvs) who
In message [EMAIL PROTECTED]
[EMAIL PROTECTED] (John Minnihan) wrote:
[EMAIL PROTECTED] wrote:
Plus I seem to recall that in CVS 1.10.8, you cannot export directories
that have default log messages specified in rcsinfo (you get an error
about not being able to create
Hi, Greg:
Greg A. Woods wrote:
[ On Thursday, October 18, 2001 at 11:49:52 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
building =//= releasing, especially when the build is already understood
to be an 'overnite' which is at the very bottom of the food chain.
Of course
[ On Wednesday, October 17, 2001 at 15:25:51 (GMT), Tom Sanidas wrote: ]
Subject: CVS export
Do I have
to go through my modules and create a fake tag for each of them before
I export, or should I just use checkout? Any suggestions?
Depending on what you use your nightly builds for, it may
[ On Wednesday, October 17, 2001 at 11:40:38 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
Why use export?
For all the same reasons you should use cvs export when checking out
any actual release.
--
Greg A. Woods
+1 416 218
[EMAIL PROTECTED] wrote:
[ On Wednesday, October 17, 2001 at 11:40:38 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
Why use export?
For all the same reasons you should use cvs export when checking out
any actual release.
building =//= releasing, especially when the build
Tom == Tom Sanidas [EMAIL PROTECTED] writes:
Tom Hi, I'm trying to use cvs export to do a nightly build sort
Tom of thing. I'm trying to get the current versions of the main
Tom trunk exported to a set of directories that I'll use to
Tom perform a build. I've tried using -D
, tag often.
I consider these periodically made tags costly, as I can
cvs export/co -D 3 months ago ...
easily. And this is virtually free. Tags also makes fills the output
of cvs log -h with rubbish.
--
Lee Sau Dan §õ¦u´°(Big5)~{@nJX6X~}(HZ
-Original Message-
From: Lee Sau Dan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 18, 2001 12:23 PM
To: [EMAIL PROTECTED]
Subject: Re: CVS export
This message uses a character set that is not supported by
the Internet Service. To view the original message content
Lee Sau Dan writes:
I usually say -D now. I know -D today would work, too, but I'm
not sure if it means midnight (00:00) of today.
It means the start of today (00:00), which is not the same as now.
-Larry Jones
Even my FRIENDS don't do what I want. -- Calvin
[ On , October 18, 2001 at 19:22:33 (+0200), Lee Sau Dan wrote: ]
Subject: Re: CVS export
easily. And this is virtually free. Tags also makes fills the output
of cvs log -h with rubbish.
Something like that is only rubbish if it doesn't mean anything to you.
To me those dates you would
[ On Thursday, October 18, 2001 at 11:49:52 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
building =//= releasing, especially when the build is already understood
to be an 'overnite' which is at the very bottom of the food chain.
Of course not -- _BUT_ that's why I qualified my
[EMAIL PROTECTED] wrote:
[ On Thursday, October 18, 2001 at 11:49:52 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
building =//= releasing, especially when the build is already understood
to be an 'overnite' which is at the very bottom of the food chain.
Of course not -- _BUT_
[ On Thursday, October 18, 2001 at 20:34:13 (-0700), John Minnihan wrote: ]
Subject: Re: CVS export
In all the years I've used CVS, I've institutionalized use of 'cvs
export' only briefly at one client. And that was only to satisfy some
nimrod (who didn't understand cvs) who screamed
Hi,
I'm trying to use cvs export to do a nightly build sort of thing.
I'm trying to get the current versions of the main trunk exported to a
set of directories that I'll use to perform a build. I've tried using
-D and today's date, but cvs misses some files that way. Do I have
to go
Tom Sanidas writes:
I'm trying to use cvs export to do a nightly build sort of thing.
I'm trying to get the current versions of the main trunk exported to a
set of directories that I'll use to perform a build. I've tried using
-D and today's date, but cvs misses some files that way
. It is
especially good at dependency analysis.
An example of this using classic make is availble here:
http://jbminn.com/misc/build.pl.txt
The BuldEnv.pm used above is here:
http://jbminn.com/misc/BuildEnv.pm.txt
[EMAIL PROTECTED] wrote:
Hi,
I'm trying to use cvs export to do a nightly
Title: Re: cvs export error when using commit templates
I think its a bug, however you can work around it by creating a sym link in your repository to an area that doesn't have a template defined, then create a project specifically for the purpose of exporting.
David
Alexandru Harsanyi
On Mon, Jul 17, 2000 at 11:19:24AM -0400, Larry Jones wrote:
You need to update either the client, the server, or both to the latest
version (1.10.8) which you can get from www.cvshome.org.
I imagine most of these problems would go away if we could just get 1.10.8
on ftp.gnu.org.
Please?
mrc
Hi,
I am having problem with the export command.
I am trying to access a remote server (Sun box).
The local machine is a Linux (mandrake 7.0) box.
Access method is :pserver:.
cvs -q export -D yesterday 3rdParty/ibm
cvs [export aborted]: Can't parse date/time: 7/15/2000 19:4:34 GMT
Any help
Ly, Nghia writes:
[nly@tstmh002 nly]$ cvs export -d test -r Test_Tag WIA
cvs [export aborted]: cannot write CVS/Template file: No such file or
directory
This is a bug in client/server CVS -- when you specify a check-in
message template for a directory in CVSROOT/rcsinfo, you can't export
CVS newbie - Sorry if this question came up before.
How can I cvs export through pserver? Is this possible? Since
"export"
is similar to checkout but without the CVS admin folders, one should
be able to 'export'. I tried but no luck.
Please help.
[EMAIL PROTECTED] writes:
How can I cvs export through pserver? Is this possible? Since
"export"
is similar to checkout but without the CVS admin folders, one should
be able to 'export'. I tried but no luck.
It should just work -- what problem are you having?
-Larry J
ry and run the above command.
Hope this helps
-Original Message-
From: Ly, Nghia [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 26, 2000 1:38 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: How to 'cvs export' through pserver?
Larry,
Thank you for replying:
Here is the output:
[nl
49 matches
Mail list logo
