Title: cannot open /nonexistant/.cvsignore: Permission denied
Hello Colleagues,
Its my second posting on the same issue.
I am relatively new to CVS and I would really appreciate if somebody could help me to understand the root cause of the problem.
I am using CVS version 1.11.17 for both
is in
Oregon. My client is in California. It runs on a PC under Windows XP using
CYGWIN_NT-5.1 1.5.13(0.122/4/2) 2005-03-01 11:01.
CVS works fine for me.
However, every time I do a check in I get an additional error message:
cvs server: cannot open /nonexistant/.cvsignore: Permission denied
SNIP
server: cannot open /nonexistant/.cvsignore: Permission denied
Every time I do a cvs update it works but every directory has an
additional error message:
cvs update: cannot open /nonexistant/.cvsignore: Permission denied
I looked into my directories. File .cvsignore is present everywhere.
Its
Well
basically I've checkout a set of jsp and java
files from a brand a repository into an eclipse project.
Then I added some gif, html, psd, class files into the checked out
folders, but wanna ignore them when doing a commit.
any way to do a global .cvsignore rather than a .cvsignore
in each
I have a whole bunch of files in my local client directory that I wanted
to ignore whenever doing and update or commit to the server.
I noticed that you can have a file called .cvsignore, but that only works
for a single client and you must have it in every directory and
subdirectory in order
OTESAO [EMAIL PROTECTED] wrote:
I have a whole bunch of files in my local client directory that I wanted
to ignore whenever doing and update or commit to the server.
[ ... ]
Not sure what you want to do but: once a file is under CVS control,
you can't ignore it. The .cvsignore and related
Hi,
i want to use
*.
in the .cvsignore file
But it does not work.
Is there a workaround?
regards
Thomas
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Thomas Bornhaupt
i want to use
*.
in the .cvsignore file
But it does not work.
Is there a workaround?
Ignore the parent directory.
--
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http
Hi Jim,
i want to use
*.
in the .cvsignore file
But it does not work.
Is there a workaround?
Ignore the parent directory.
Ignore the parent directory is
*.*
and this would work.
I want to ignore
*.
my C-Compiler creates binary files without extension. But this files
Of
Jim.Hyslop
Sent: Tuesday, January 11, 2005 9:29 AM
To: info-cvs@gnu.org
Subject: RE: .cvsignore *.
Thomas Bornhaupt
i want to use
*.
in the .cvsignore file
But it does not work.
Is there a workaround?
Ignore the parent directory.
--
Jim Hyslop
Senior Software Designer
Leitch Technology
Thomas Bornhaupt wrote:
my C-Compiler creates binary files without extension. But
this files are not
nessesary in the CVS
Oh, I see. Sorry about the misunderstanding.
I don't think you can do what you want directly - I believe the .cvsignore
is simply a wildcard matching format (as opposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bornhaupt [EMAIL PROTECTED] writes:
Hi Jim,
i want to use
*.
in the .cvsignore file
But it does not work.
Is there a workaround?
Ignore the parent directory.
Ignore the parent directory
Thomas Bornhaupt wrote:
I want to ignore
*.
my C-Compiler creates binary files without extension. But this files are not
nessesary in the CVS
Are you running on a Unix system? If so, then *. matches
files with a period as the last character. Files without an
extension may not have that period.
Hi Frederic,
If you are running on a Windows system and using CVSNT
version 2.0.51d (the one I tested with), then '*' matches a
file without an extension. Unfortunately, it also matches
all files.
i work still with 2.0.18. (never change a winning team) but i look for a
newer on
But .cvsignore ignors '*.'
I put the name explicit in the .cvsignore file. This work. But so i have to
change all the .cvsignore files.
Thomas
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
extension in the .cvsignore file. This work.
but there was an other nice think. I use TortoiseCVS. And have a new project
in a new direktory. If i make an add ('CVS Inhalt hinzufügen') to the parent
directory. The new dirctory would be added but also my file without
extension. The .cvsignore file
Hi,
all together now:
*. (files without extension) does not work in the .cvsignore with CVSNT
2.0.58b and Windowes.
the tipp:
[-_a-zA-Z0-9]*\.
does also not work.
Regards
Thomas
(it is not a bug, it is a featcher)
___
Info-cvs mailing list
Info
Thomas,
i work still with 2.0.18.
This is CVSNT (check with cvs -v on the command line). Please direct all CVSNT
questions to the CVSNT mailing list:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.cvsnt
The current version is 2.0.58d - but I do not know
a kernel source for personal
modifications. Well, kernel contains some directories called core
which are ignored because it's included in the list of files/directory
to be ignored. Actually I can see:
I core
while importing.
I had a look at cvsignore docs:
http://docs.freebsd.org/info/cvs
while importing.
I had a look at cvsignore docs:
http://docs.freebsd.org/info/cvs/cvs.info.cvsignore.html
so it says that I can _add_ new files to be ignored, mmm so can I modify
this list?. Actually I created a file cvsignore:
[EMAIL PROTECTED]:/home/cvs# cat CVSROOT/cvsignore
RCS
Hi,
Im tring to block files with extensions that
I dont want the users send to the repository. I begin trying to block ZIP
files.
I created the cvsignore file in
CVSROOT.
*.zip
I doesnt work first time, so I checked in the
output Window of WinCVS that it sendthe -I ! parameter
Diego Ribeiro de Andrade wrote:
Im tring to block files with extensions that I dont want the
users send to the repository. I begin trying to block ZIP files.
Well, you might want to rethink that. There are times I have needed to check
in zip files, for specific reasons (certain files, provided
Purushotham Komaravolu [mailto:[EMAIL PROTECTED] wrote:
Can somebody tell me how to setup cvsignore for the entire
repository.
I added the attached file to the repository/CVSROOT folder,
but it dint
work.
Just a shot in the dark here, but did you add cvsignore to
CVSROOT
Hello,
Can somebody tell me how to setup cvsignore for the entire
repository.
I added the attached file to the repository/CVSROOT folder, but it dint
work. i.e I created a test.class and tried to add *.* to repository, CVS
should ignore that file.. but it dint
Thanks
Puru
Purushotham Komaravolu writes:
This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
I added the attached file to the repository/CVSROOT folder, but it dint
work. i.e I created a test.class and tried to
On Wed, 2003-10-22 at 15:47, Gisbert Amm wrote:
checking out the CVSROOT from the network will return an error
~$ cvs co CVSROOT
cvs server: cannot open /root/.cvsignore: Permission denied
cvs server: Updating CVSROOT
U CVSROOT/checkoutlist
snip
~$
but if i will checkout
On Wed, 2003-10-22 at 16:16, Gisbert Amm wrote:
As which user do you checkout the CVSROOT directory on the remote host?
uhuh... by using pserver logging in the user both remote and local im
still having the
'cvs server: cannot open /root/.cvsignore: Permission denied'
what am i missing
]$
##checking out the CVSROOT
[EMAIL PROTECTED] repo]$ cvs co CVSROOT
cvs server: cannot open /root/.cvsignore: Permission denied
cvs server: Updating CVSROOT
U CVSROOT/checkoutlist
U CVSROOT/commitinfo
U CVSROOT/config
U CVSROOT/cvswrappers
U CVSROOT/editinfo
U CVSROOT/loginfo
U CVSROOT/modules
U
do a grep /root/.cvsignore within CVSROOT already?
not yet
BTW: The error is annoying but should not prevent you from working with cvs.
AFAIS the checkout works correctly.
yah i just noticed it and i tried to refer to the group...
Gisbert Amm
-Original Message-
From
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
By default, cvs will try to add ~/.cvsignore to the wildcards found in
$CVSROOT/CVSROOT/cvsignore, ~/.cvsignore and in the CVSIGNORE
environment variable. As root is starting the cvs server side of the
connection it would seem likely that ~root
kent emia writes:
~$ cvs co CVSROOT
cvs server: cannot open /root/.cvsignore: Permission denied
You're running an old version of CVS on the server and you have $HOME
set in the server's environment, either because you've explicitly set it
or because [x]inetd has (erroneously) set it for you
checking out the CVSROOT from the network will return an error
~$ cvs co CVSROOT
cvs server: cannot open /root/.cvsignore: Permission denied
cvs server: Updating CVSROOT
U CVSROOT/checkoutlist
snip
~$
but if i will checkout the CVSROOT in the server theres no error
--
kent emia [EMAIL
We should have been happy with running make distclean before running
cvs import.
(snip)
find . -print | xargs rm
We use cvs in our IDE for the customers. Upon creation of a project there
are already many source files from the (embedded) OS. These files are
already precompiled as a
Kaz Kylheku writes:
This is as it should be. The TYPES file represents the project's
policy; some random user command should not override that policy. If we
don't want .exe files in the repository, the add command should defend
that decision for us, even if weakly.
I happen to disagree,
On Wed, Jun 04, 2003 at 02:19:44PM -0700, Peschko, Edward wrote:
[ Larry Jones wrote:]
Damn straight. If you want software that thinks it knows more than you
etc...
But that goes contrary to the dictum there's more than one way to do it.
Umm, you've got the wrong Larry :-)
No way is
are still being
collected :-)
I agree that cvs add does just what it should do, but I can understand
the desire for a cvs add-with-ignore command.
It wouldn't be too hard to write a shell script cvs-my-add that trimmed
the list of files on the command line based on the contents of ./.cvsignore
: Greg A. Woods [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 9:58 PM
To: CVS-II Discussion Mailing List
Subject: Re: .cvsignore file being ignored
[ On Wednesday, June 4, 2003 at 16:34:23 (-0700), Peschko,
Edward wrote: ]
Subject:
It is in the sense that you are forcing
Peschko, Edward writes:
Why the resistance to what would be a trivial feature?
Because even trivial features are expensive. They clutter up the code,
the test suite, the documentation, and the users' minds. In this case,
it encourages a bad, some would even say dangerous, habbit (expecting
If we don't want .exe files in the repository, the add command should defend that
decision for us, even if weakly.
I happen to disagree strongly . . . There's nothing I hate more than software that
knows
more than I do.. etc. etc. etc
But that's what I don't understand. The idea behind
[ On Thursday, June 5, 2003 at 11:42:37 (-0700), Peschko, Edward wrote: ]
Subject: Re: .cvsignore file being ignored
But that's what I don't understand. The idea behind .cvsblock (or TYPES or whatever)
is to be able
to *customize* the software to be able to exclude files.
What you don't
But that's what I don't understand. The idea behind .cvsblock (or TYPES or whatever)
is to be able
I think that .cvsblock is silly; the tiny semantics difference between
that and .cvsignore is not worth it. The cvs add command should ignore
things that match .cvsignore, period. Those who disagree
[ On Thursday, June 5, 2003 at 14:00:12 (-0700), Kaz Kylheku wrote: ]
Subject: Re: .cvsignore file being ignored
I think that .cvsblock is silly; the tiny semantics difference between
that and .cvsignore is not worth it. The cvs add command should ignore
things that match .cvsignore, period
--- Forwarded mail from Greg Woods:
[ On Thursday, June 5, 2003 at 14:00:12 (-0700), Kaz Kylheku wrote: ]
Subject: Re: .cvsignore file being ignored
I think that .cvsblock is silly; the tiny semantics difference between
that and .cvsignore is not worth it. The cvs add command should ignore
[ On Thursday, June 5, 2003 at 15:23:16 (-0700), Paul Sander wrote: ]
Subject: Re: .cvsignore file being ignored
I agree with the first part, but I don't believe that the second part
was really considered by the designer and the implementation came out
the way it did by default.
Actually
Paul Sander [EMAIL PROTECTED] writes:
Consider the use of cvs import, which obeys the .cvsignore file.
Yes, that 'cvs import' obeys the .cvsignore file is somewhat broken.
The '-I !' command-line option should be honored and should NOT process
either local .cvsignore files or the global
not be committed.
No, the big thing to remember that is different between import and add
is that add takes an explicit list of files to process whereas import
does not. .cvsignore *never* overrides an explicit file specification
by the user (nor should it), it only affects what files CVS processes
No.
A user should be able to add any file to the repository that they wish
The .cvsignore file is to reduce the clutter on an update or diff
I disagree. If I say 'cvs add * in a directory, I surely don't want to pick up extra
files, like vim's .swp, and ~ files,
or maybe .bak files
Peschko, Edward writes [in long lines]:
I disagree. If I say 'cvs add * in a directory, I surely don't want to pick up extra
files, like vim's .swp, and ~ files,
or maybe .bak files, or whatever.
Then don't say that. Or follow it with a cvs rm *.swp ... to unadd
the stuff that you didn't
I disagree. If I say 'cvs add * in a directory, I surely don't want to pick up extra
files, like vim's .swp and ~ files.,
Then don't say that. Or follow it with a cvs rm *.swp ... to unadd
the stuff you didn't really want to add in the first place. But
don't complain when CVS does exactly
Peschko, Edward writes [still using long lines]:
But that's no good - its error prone, and it puts the onus on the user to get it
right.
Damn straight. If you want software that thinks it knows more than you
do, Microsoft will be glad to oblige you. The philosophy here is that
the user is
But that's no good - its error prone, and it puts the onus on the user to get it
right.
Damn straight. If you want software that thinks it knows more than you
etc...
But that goes contrary to the dictum there's more than one way to do it. You didn't
comment
on my .cvsblock proposal -
[ On Wednesday, June 4, 2003 at 13:04:30 (-0700), Peschko, Edward wrote: ]
Subject: Re: .cvsignore file being ignored...
I disagree. If I say 'cvs add * in a directory, I surely don't want to
pick up extra files, like vim's .swp, and ~ files, or maybe .bak
files, or whatever.
Regardless
[ On Wednesday, June 4, 2003 at 13:41:14 (-0700), Peschko, Edward wrote: ]
Subject: Re: .cvsignore file being ignored...
But that's no good - its error prone,
Ah, NO, it is definitely _not_ error prone!
and it puts the onus on the user to get it right. If I'm a cvs
administrator working
On Wed, Jun 04, 2003 at 07:11:07PM -0400, Greg A. Woods wrote:
[[ PLEASE DO NOT TRY TO RESPOND TO ME DIRECTLY WHEN YOU CC THE LIST,
and if you do not want me to do so in return then set your reply-to
header appropriately ]]
It is not possible for me to set my 'reply-to header'
like '--force'
That would be minutely better than your next suggestion, but its still really
very unnecessary and would seriously break backward compatibility... etc
That's why I suggested a new feature.
[about .cvsblock ] Then who gets to mediate between that and the existing .cvsignore
list
On Wed, 4 Jun 2003, Peschko, Edward wrote:
No need for mediation. The point of .cvsblock would be to scan, and filter,
arguments on the
You want it, you hack it!
Meta-CVS works as you want. It has a TYPES file which can specify that
files having a certain suffix ought to be added using a
[[ PLEASE DO NOT TRY TO RESPOND TO ME DIRECTLY WHEN YOU CC THE LIST,
and if you do not want me to do so in return then set your reply-to
header appropriately ]]
[ On Wednesday, June 4, 2003 at 15:48:58 (-0700), Peschko, Edward wrote: ]
Subject: Re: .cvsignore file being ignored
The more
such people then it is your duty to teach them to use
their tools more properly!
Why not change CVS and let them do this
Because it's FAR too late for such a fundamental change. You can't just
arbitrarily invert the way the UI and a key feature like the .cvsignore
file works in a widely used tool
hm.
I have a .cvsignore file in each of my directories with the following entry:
*~
and yet when I say:
cvs add file~
it happily accepts the file, puts it in for committing. when I cvs commit, it commits
the file.
umm... shouldn't .cvsignore block these entries from being even processed
Peschko, Edward [EMAIL PROTECTED] writes:
hm.
I have a .cvsignore file in each of my directories with the following entry:
*~
and yet when I say:
cvs add file~
it happily accepts the file, puts it in for committing. when I cvs
commit, it commits the file.
umm... shouldn't
hi all,
I have a project which produces HTML output into a subfolder called HTML.
I want to ignore the folder because I produce it with my build script.
However, .cvsignore only ignores files. Any way around this?
TIA,
Matthew Herrmann
--
Far Edge Technology
Matthew Herrmann writes:
However, .cvsignore only ignores files. Any way around this?
.cvsignore ignores both files and directories. However, if CVS had
already noted that a subdirectory exists *before* you added it to
.cvsignore, it will continue to process it. To correct that, edit the
CVS
I can't get the $CVSROOT/CVSROOT/cvsignore file to
work correctly (what I think it should do :)). I put a single line entry
with
vssver.scc
on it to keep these files from importing (we're
migrating some projects from Visual SourceSafe), but they get
importedand/or recognized as unknown
Cary Coulter writes:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary80217196335194441==
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
I can't get the $CVSROOT/CVSROOT/cvsignore file to work correctly (what
I think
I am using WinCVS. Setting the CVSIGNORE environment variable,
either for user or system, does not seem to work. Does anyone know
what will work. I would prefer to avoid changing CVSROOT/.cvsignore
if possible, as that tends to change things for everyone on all projects.
TiA,
/|/|ike
What will happen if a cvs command (say for instance cvs import)
finds a **directory** named core, which by default *is* in the cvs
ignore list? Will it ignore any files in this directory?
/npat
--
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship,
[EMAIL PROTECTED] writes:
What will happen if a cvs command (say for instance cvs import)
finds a **directory** named core, which by default *is* in the cvs
ignore list? Will it ignore any files in this directory?
Yes.
-Larry Jones
I stand FIRM in my belief of what's right! I REFUSE to
Larry Jones wrote:
[EMAIL PROTECTED] writes:
What will happen if a cvs command (say for instance cvs import)
finds a **directory** named core, which by default *is* in the cvs
ignore list? Will it ignore any files in this directory?
Yes.
This happened the other day while I was
I've had success making a cvsignore file work in a specific directory, by
placing the file in that directory, but I'm pretty sure that you should be
able to make an ignore file work globally
(i.e. block out all .bak files no matter how far down the tree structure).
I've tried the help files
hi,
Is it possible to exclude whole directories via the .cvsignore mechanism? If
yes, how? I've added the directory names to exclude to the .cvsignore file at
the same point in the heirarchy as the directories I want ignored, but cvs still
includes them.
cheers
Nathan
Nathan Coast writes:
Is it possible to exclude whole directories via the .cvsignore mechanism? If
yes, how? I've added the directory names to exclude to the .cvsignore file at
the same point in the heirarchy as the directories I want ignored, but cvs still
includes them.
Yes it's
My local respository is in /usr/local/cvsroot.
I went into my working area and issued...
cvs -d /usr/local/cvsroot/ co CVSROOT
... I then changed into the new working area subdirectory of CVSROOT and
issued...
echo *.class *.txt *.jar cvsignore
cvs add cvsignore
cvs commit -m New file
[EMAIL PROTECTED] (Larry Jones) wrote in message
news:[EMAIL PROTECTED]...
[EMAIL PROTECTED] writes:
currently, my $CVSROOT/CVSROOT dir does not contains a cvsignore file. Is
it sufficient to simply create the file in the directory,
or do I need to checkout CVSROOT, and 'cvs add
Hi,
I am having problems trying to avoid some files using cvsignore file.
When I created it using the following command,
echo *.class *.txt *.jar $CVSROOT/CVSROOT/cvsignore
chmod ug+rwx,o-rwx !$
and did a cvs import (using a normal user account), all .class files
get imported. Here
Eric Siegerman wrote:
On Fri, Dec 14, 2001 at 03:30:31PM -0500, Jack Baty wrote:
My problem is that I don't know if there's a way to cvsignore all files
*except* the .cvsignore file within each directory.
Put an entry * in .cvsignore.
If a file is already CVS-tracked, that takes
,
since they will never belong in the repository. I'm trying to solve this
with a .cvsignore.
My problem is that I don't know if there's a way to cvsignore all files
*except* the .cvsignore file within each directory.
Unless there's a better way to handle this altogether.
Let me know if I've
On Fri, Dec 14, 2001 at 03:30:31PM -0500, Jack Baty wrote:
My problem is that I don't know if there's a way to cvsignore all files
*except* the .cvsignore file within each directory.
Put an entry * in .cvsignore.
If a file is already CVS-tracked, that takes priority over a
.cvsignore entry
I'm using CVS for web app development. I typically keep a /config directory
for things like local settings (database login, file paths, etc.). I'm having
a tough time figuring out how to manage these files. I'd like to make sure
that whenever someone checks out the module that they get the
I'm trying to ignore a whole directory in a cvs module, but it simply isnt
working. I have a .cvsignore file in the directory above, where one file and
the directory name is entered. the file is always ignored, when updating,
but the directory and all its files always are shown when updating
Regarding cvsignore the Cederqvist manual says
The per-repository list in `$CVSROOT/CVSROOT/cvsignore' is appended to
the list, if that file exists.
currently, my $CVSROOT/CVSROOT dir does not contains a cvsignore file. Is
it sufficient to simply create the file in the directory,
or do I need
[EMAIL PROTECTED] writes:
currently, my $CVSROOT/CVSROOT dir does not contains a cvsignore file. Is
it sufficient to simply create the file in the directory,
or do I need to checkout CVSROOT, and 'cvs add' the cvsignore file?
Simply creating the file is sufficient, but checkout and add
Ken Hu writes:
I've run into the following problem and I found the answer in the manual.
But I am sure that I have set -f parameter in my inetd.conf file.
So , any idea why this still occurs ?
Because you're running on a version of Linux where inetd incorrectly
sets $HOME for the processes
but get errors like:
cvs server: cannot open /root/.cvsignore: Permission denied
cvs [server aborted]: can¡¦t chdir(/root): Permission denied
then you probably haven¡¦t specified ¡¥-f¡¦ in ¡¥inetd.conf
and check out anything through wincvs it simply reports
that it was unable to chdir into /root so that it could read .cvsignore
I can't remember ever saying that it should find .cvsignore in the root
users folder so why is it looking there (of all places).
I am pretty sure this is a fairly simple
doozer writes:
Every time I try and check out anything through wincvs it simply reports
that it was unable to chdir into /root so that it could read .cvsignore
You omitted the -f from the CVS command line in /etc/inetd.conf.
-Larry Jones
He's just jealous because I accomplish so much more
Why error /root/.cvsignore can not open. permission denied.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
When I try to checkout (from WinCVS. Repository is on unix box.) I get this
error:
cvs server: cannot open /homeroot/.cvsignore: Permission denied
Note 1: /homeroot is the actually home directory for the unix user root.
Note 2: I am not root. I am cvsadmin and the entire software
Check the documentation:
http://faq.cvshome.org/fom-server/cache/23.html
donald
On Mon, Jun 04, 2001 at 06:00:32PM -0700, Schwenk, Jeanie wrote:
When I try to checkout (from WinCVS. Repository is on unix box.) I get this
error:
cvs server: cannot open /homeroot/.cvsignore: Permission
Hi, I've checked out CVS sometime ago from cvs.cvshome.org,
and now I do:
[scameron@zuul ccvs]$ cvs -z3 -nq update
? lib/.deps/argmatch.Po
? lib/.deps/dup2.Po
? lib/.deps/fncase.Po
[ ... loads more ? files...]
? src/.deps/[loads of ? files...]
Should there be .cvsignore entries
Stephen Cameron writes:
Should there be .cvsignore entries for these .deps directories?
There are.
-Larry Jones
I'm crying because out there he's gone, but he's not gone inside me. -- Calvin
___
Info-cvs mailing list
[EMAIL PROTECTED]
http
there be .cvsignore entries for these .deps directories?
Or is there a reason not to?
These directories were briefly checked into CVS because of a mistake of
mine. I've since deleted them from the repository, but for one reason
or another CVS kept checking out the empty directory, or perhaps, more
George Mathew writes:
I am trying not to ignore the core directory during cvs import.
I added a cvsignore file in $CVSROOT/$CVSROOT directory of server.
[...]
This did not work.
But if I add this to my $HOME/.cvsignore file it works.
The documentation says $CVSROOT/$CVSROOT is the first
I am trying not to ignore the core directory during cvs import.
I added a cvsignore file in $CVSROOT/$CVSROOT directory of server.
This cvsignore file contains:
!
RCS SCCSCVS CVS.adm
RCSLOG cvslog.*
tagsTAGS
.make.state .nse_depinfo
On Mon, Apr 23, 2001 at 02:00:15PM +0100, Geraint Evans wrote:
I keep getting the following error whenever I try to do anything:
cannot open /root/.cvsignore: Permission denied
I am using pserver to access a remote repository. The error is
intermittent - sometimes everything works fine
Hi
I keep getting the following error whenever I try to do anything:
cannot open /root/.cvsignore: Permission denied
I am using pserver to access a remote repository. The error is
intermittent - sometimes everything works fine and other times I can't do
anything. The person who is hosting
Hi,
In one of the directories in our CVS tree we build executables which
obviously we don't want to be committed in the tree. For example:
.
\- Translator
\- Binaries.Linux.i386
Translator is in the tree, but Binaries is created by the makefiles.
There is a .cvsignore file in Translator
On Mon, Mar 12, 2001 at 03:53:07PM -, [EMAIL PROTECTED] wrote:
.
\- Translator
\- Binaries.Linux.i386
Translator is in the tree, but Binaries is created by the makefiles.
There is a .cvsignore file in Translator which contains the line
"Binaries.*". However, when I run
Greetings, all.
I've got a question about .cvsignore and previously-deleted files. (This
is independent of the other thread discussing possible additions to the
default .cvsignore file.)
In the module I'm working on, there is a file called productInfo.cc. This
file used to be in the CVS
s far
from a common convention. Conservativeness argues against
ignoring them by default.
ID GNU id-utils database file
Likewise. I have this in my ~/.cvsignore, but I doubt it should
be in the default list, since it's only a generated file on those
systems that hap
;objs" to
my .cvsignore file, would it not be ignored because its a directory?
Not so good... Short of rewiring the cvsignore so you can specify
a file type, I don't think there's much to do about this problem.
For example, a file named "core" should be ignored. But a directory
1 - 100 of 171 matches
Mail list logo
