-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sensei <[EMAIL PROTECTED]> writes:
> Hi. I'm new to branching, I always used it just as tagging versions,
> never joining back with head... so pleas excuse me being naive :)
>
> I'd like to know if it's possible to know the exact date when a
> branch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hridyesh Pant <[EMAIL PROTECTED]> writes:
> Hi All,
> My cvs tag command is suddenly taking too much time while tagging a code of
> 2GB .It is affecting our performance. My system configuration after top
> command is as below
>
> 11:47am up 66 day
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buozis, Martynas <[EMAIL PROTECTED]> writes:
> Is it possible to import data from CCASE into CVS ? If yes - how ?
> Thanks.
You should use a search engine to find prior art... something like
this describes how you might go about writing one for yours
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S I <[EMAIL PROTECTED]> writes:
> Thank you. I'm not sure what /bin/test represents? To be replaced with
> the path to my proj?
It represents the /bin/test (see 'man test' on your GNU/Linux box for
more details) command to compare the output of the `
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S I <[EMAIL PROTECTED]> writes:
> Hi everyone,
>
> I'm planning to lock cvs today getting ready for our release. I
> realize with certain version control software nowadays you don't have
> to lock the repo and the developers can continue with their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
These two lines need to dispose of stdin:
Original:
project1 (chgrp -Rf project1 /usr/local/cvsroot/project1)
project2 (chgrp -Rf project2 /usr/local/cvsroot/project2)
Revised:
project1 (chgrp -Rf project1 /usr/local/cvsroot/project1; cat) >/dev/n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yu He <[EMAIL PROTECTED]> writes:
> Thanks a lot for your reminding.
>
> - host OS information for server: Redhat 9
> - host OS information for client: Window 2000
> - server version of cvs: cvs 1.11.6
> - client version of cvs: wincvs 1.3
> - n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yu He <[EMAIL PROTECTED]> writes:
> Hi all:
> After commit,always receive the following error message,
> cvs [server aborted]: received broken pipe signal
>
> What's the reason?
>
> Thanks a lot in advance!
You have provided insufficient informat
s error
>
> regards
Note: You should consider getting a compiler that is able to deal with
ANSI C. Future releases of CVS (1.12.x) will give you many problems
otherwise as that release of CVS assumes a C89 capable standalone
compiler.
Does the following patch fix your problem?
-- Mark
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
>
> >>The only problem now is that if a cvsadmin user introduces a directory
> >>into the cvs repository using "add", the directory is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius <[EMAIL PROTECTED]> writes:
> The only problem now is that if a cvsadmin user introduces a directory
> into the cvs repository using "add", the directory is owned by him, not
> by the global cvs user, and nobody else can check into/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<[EMAIL PROTECTED]> writes:
> Is there a version of CVS that runs on FreeBSD?
There are many such versions. FreeBSD has been using cvs for development
for many years.
> I only see versions for other Unix platforms, just nothing that
> explicitly say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<[EMAIL PROTECTED]> writes:
> I'm a newbie when it comes to compiling from source files, so i really
> appreciate any help you all can offer. Thanks again! X
> <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Is there a version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Opificius <[EMAIL PROTECTED]> writes:
> Larry Jones wrote:
> > Julian Opificius writes:
> >
> >>I'm not quite sure what you mean by "mapping" users.
> > Using the third field of the CVSROOT/passwd file to have the server
> > run
> > as some use
generally
useful for normal operation.
=back
=head1 LICENSING
find-locks.perl - locate and possibly remove stale cvs locks
Copyright (c) 2003, 2004 by Mark D. Baushke <[EMAIL PROTECTED]>
All rights reserved.
This program is free software; you can redistribute it and/or modify
it und
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Jackson <[EMAIL PROTECTED]> writes:
> Ok, if there is a directory in a project that had three files in it
> and they were all removed to the attic with cvs rm at different times
> and you want to recover all three files (say 3 could be 100+ file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Spiro Trikaliotis <[EMAIL PROTECTED]> writes:
> I just upgraded to 1.12.9 (from 1.11.x) and I am a little bit confused
> about the new loginfo format.
>
> My current loginfo looks like:
>
> DEFAULT Mail -s %1s [EMAIL PROTECTED]
>
> Now, I've read
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
prithisd @yahoo.com <[EMAIL PROTECTED]> writes:
> Hai,
>
> I am facing problem in downloadibg the whole directory
> structure from,
>
> http://cvs.sourceforge.net/viewcvs.py/translate/po/
>
> Help me please.
Why is this our problem?
Go to http://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tim,
Tim Allen <[EMAIL PROTECTED]> writes:
> I've been using CVS 1.11.17 clients (and earlier versions) on Windows
> machines with no problems. The CVS server runs on a Linux 2.4 box. Access is
> over SSH, using the Cygwin OpenSSH, using digital c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mainak Sen <[EMAIL PROTECTED]> writes:
> Hi,
> Can someone help me with the solution to the following problem ?
>
> I want to selectively give write access to some subdirectories for
> some people. How can this be done ?
>
> Thanks a lot in advance,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
vik <[EMAIL PROTECTED]> writes:
> I searched for and found a post on exactly this same topic on this
> group, and though it was helpfull, I couldnt figure out the technical
> details. So could someone please help me out?
>
> I am looking for a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pginfo <[EMAIL PROTECTED]> writes:
> thanks for answer.
>
> I searched NetBeans.org for solution of my problem and found this one :
>
> http://www.netbeans.org/issues/show_bug.cgi?id=39919
Ahhh... cvs 1.11.12 is the one where the Case request-type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have no idea what you mean by 'case' commands in cvs or Netbeans.
I suspect you are running into an error that is not directly related to
cvs and may instead be related to your command environment.
As to your problem with cvs 1.11 (which is ancient
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ankush grover <[EMAIL PROTECTED]> writes:
> This is my first post on CVS mailing list.I have 2 problems.
Well, given you are planning to use :pserver: which is not really
secure, you have three problems...
> a) I have configured CVS on Fedora Core 3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
farseer <[EMAIL PROTECTED]> writes:
> thanks for the response. I am not well versed in the unix/linux
> commands. as such, i am wondering if you may be able to assist further:
>
> 1) How can i create a group?
This varies by operating system. The 'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bulgrien, Kevin <[EMAIL PROTECTED]> writes:
> The original question was:
>
> A user did a cvs init on an existing repository. Is this generally safe,
> or might it be advisable to go back and check for differences against a
> backup?
A 'cvs init' i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Satishkumar <[EMAIL PROTECTED]> writes:
> Can any one help in fixing this error. please
>
> cvs commit -m "MICS Id:104226 \nDescription:adding new files " ehelp.xml (in
> directory E:\en-US)
>
> cvs [server aborted]: received abort signal
>
> cvs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S I <[EMAIL PROTECTED]> writes:
> Is there any way to force the users to comment or annotate their
> commits or checkins?
Yes. via 'verifymsg' read
https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC167
> I know by default the -m "commen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please do not use HTML e-mail.
Zeus Crisp <[EMAIL PROTECTED]> writes:
> Hello all,
>
> Hoping someone can help as I am a new users to CVS.
>
> I would like to know if there is a way to lock a specific branch to
> block commits within a CVS enviro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fei Li <[EMAIL PROTECTED]> writes:
> How to get a CVS server and client web site http://cvshome.org
http://viewcvs.sourceforge.net
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFChAhj3x41pRYZE/gRAg77AJwKnO6V/8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrice Durosay <[EMAIL PROTECTED]> writes:
> I installed cvs & prerequisite packages on a solaris 8 server :
> diffutils-2.8.1-sol8-sparc-local.gz
> rcs-5.7-sol8-sparc-local.gz
> cvs-1.11.19-sol8-sparc-local.gz
All you should have needed as
cvs-1.11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arno Schuring <[EMAIL PROTECTED]> writes:
> > Venkatesh, Vijay <[EMAIL PROTECTED]> writes:
> >
> >> I guess this is a fairly often asked question
> >> but just wanted to run this by everyone to get
> >> some feedback first. (am referring to the
> >> e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S I <[EMAIL PROTECTED]> writes:
> OK, topleveladmin on the server is set to NO. Should it be set to yes?
It should be set to do what you intend to see done. The default is NO.
> But per Richard or Arno, I renamed the cvs subdir (to mycvs) and I'm
>
; Steve
>
> Original Message Follows
> From: "Mark D. Baushke" <[EMAIL PROTECTED]>
> To: "Arno Schuring" <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], info-cvs@gnu.org
> Subject: Re: Can't checkout to my C: root directly *PANIC* Admin Files
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arno Schuring <[EMAIL PROTECTED]> writes:
> I'm not sure, but I might have (at least) a clue for you...
>
> >Hi
> >
> >I've tried 4 or 5 different Windows command-line versions of cvs.exe from
> >(1.10.5 to 1.11.20). Created a folder called cvs dire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Wood <[EMAIL PROTECTED]> writes:
> >>for bash or other bourne shell variations use:
> CVS_RSH=/usr/bin/ssh; export CVS_RSH
>
> Thanks for that hint. I was doing it a slightly different way, which I
> thought was working as echo $CVS_RSH work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit Ruesing <[EMAIL PROTECTED]> writes:
> how is it achieved that FreeBSD users can receive src files via cvsup
> that are tagged with a RELEASE tag (RELENG_4, RELENG_5,...) while the
> branch is under further development?
Typically, they instal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Venkatesh, Vijay <[EMAIL PROTECTED]> writes:
> I guess this is a fairly often asked question
> but just wanted to run this by everyone to get
> some feedback first. (am referring to the
> essential cvs guidebook)
>
> Have two branches app4 and app4_t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Wood <[EMAIL PROTECTED]> writes:
> I'm ignoring the problem on Windows for the time being because theres a
> separate mailing list for Tortoise CVS, but on OS X, where I'm running the
> normal Unix version of CVS, my OpenSSH client is at
> /usr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Khurram Rashid <[EMAIL PROTECTED]> writes:
> I just wanted to know if there is any way in CVS to do validation
> check in,
No, CVS is the wrong tool for your task.
> i.e.
>
> Developer checks out a module from CVS
>
> Developer makes some changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muller <[EMAIL PROTECTED]> writes:
> I need a fature in version 1.12 of cvs
> (post-tagging hook).
For what it is worth, backporting that single
feature to cvs 1.11.x should not be that hard for
you to do...
> How stable is the 1.12 branch?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
You may need to see if CVS/Template is getting
properly setup. I believe that a cvs 1.11.x server
does not update that file via a 'cvs update' while
a cvs 1.12.x server does update it.
If you checkout a new tree, you should see the new
te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arthur Barrett <[EMAIL PROTECTED]> writes:
> >>>hello, i downloaded cvs-1-11-20.zip from https://ccvs.cvshome.org but
> >>>i can=B4t find information about wich windows versions are supported.
> >>>Is Windows 2003 server suitable for cvs server ?
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
twoeyedhuman <[EMAIL PROTECTED]> writes:
> Okay, I used the advice to not install cvs as root, although for
> permission reasons i did do some cvs commands as root. I don't know
> why but I still can't commit files, even if i'm not root. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
twoeyedhuman <[EMAIL PROTECTED]> writes:
> Is it possible to have a different ssh key for each user that logs into
> my cvs server?
Yes, you just want to configure your server to allow logins which give
each user their own home directory and ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
twoeyedhuman <[EMAIL PROTECTED]> writes:
> I see. So i can't edit things as root. But, can I still install cvs
> as root?
I suppose you could. I would not recommend it.
I usually verify the tarball's gpg signature, unpack the tarball,
configur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Horst Jäger <[EMAIL PROTECTED]> writes:
> I need to know my own ssh-key to work with a remote cvs repository. I
> use a Win 98 Machine.
>
> Any ideas how I can get it? The known-hosts-file only contains the
> ssh-keys oft the remote-server.
You prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muller <[EMAIL PROTECTED]> writes:
> I have a "staging" sandbox that I would like to keep up-to-date with
> the versions of my files tagged as "release candidates" (tag name:
> "RC").
>
> My original plan was to put a command in the .taginfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
twoeyedhuman <[EMAIL PROTECTED]> writes:
> When I tried to "cvs edit config", nothing showed up, and when I tried
> to "cvs commit config" it said "root" is not allowed to edit files.
> Does anyone know what's wrong?
Be default cvs is configured
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Klinke <[EMAIL PROTECTED]> writes:
> On Thursday 21 April 2005 17:27, Manuel Ledesma wrote:
>
> > I was using CVS in local machine fine; running on top of
> > Fedore Core 4. my cvs version is 1.11.20 and after updating
> > my syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel Ledesma <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
> >Manuel Ledesma <[EMAIL PROTECTED]> writes:
> >>Mark D. Baushke wrote:
> >>>Manuel Ledesma <[EMAIL PROTECTED]> writes:
> >&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel Ledesma <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
>
> >Manuel Ledesma <[EMAIL PROTECTED]> writes:
> >>I was using CVS in local machine fine; running on top of Fedore Core 4.
> >>my cv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel Ledesma <[EMAIL PROTECTED]> writes:
> I was using CVS in local machine fine; running on top of Fedore Core 4.
> my cvs version is 1.11.20 and after updating my system, I started
> getting this error:
>
> cvs [login aborted]: unrecognized auth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vijay SP. <[EMAIL PROTECTED]> writes:
> I have a requirement to lock a branch just before the release. I tried
> to browse thru the documentation and did get some idea.
> Has someone implemented it?
You can do this with the contrib/cvs_acls file.
Ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Pierre Sevigny <[EMAIL PROTECTED]> writes:
> Thanks,
>
> I guess tagging the module file at the same time of tagging the module
> would allow to keep track of the module evolution?
Possibly, but cvs would not be able to use that version of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Pierre Sevigny <[EMAIL PROTECTED]> writes:
> Modules are cool!
Modules have problems as they may be changed over time making it
difficult to recapture the state of a checkout from the past.
Modules are not branched, so the same module file need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lewis <[EMAIL PROTECTED]> writes:
> As part of an evaluation I am undertaking, it is necessary for me to
> analyse the entire diff output generated by a CVS repository. I wish to
> look at statistics such as who is responsible for the percentage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nukala Srinivas Reddy <[EMAIL PROTECTED]> writes:
> I have installed CVS server and did some testing.
Good for you. Did you install a cvs 1.11.x or a cvs 1.12.x version?
> Our requirement is to support development at multisite.
Okay.
> I think CVS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> I am trying to enable write proxy functionality by using
> CVS-1.12-11.But I have problem because primary servers will not
> automatically push changes to secondary server although I has set
> loginfo,postadmin,postwa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paras jain <[EMAIL PROTECTED]> writes:
> Thanks Russ, (Sorry Russ please ignore previous mail)
>
> >>You can test this by creating a script with the above as contents.
> >>Run it with args: a b "b a". Then remove the quotes from the $@ ant
> >>try i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Lancisi <[EMAIL PROTECTED]> writes:
> We have an offsite lab that currently pulls test suites from our cvs
> repository at our home office while running tests.. Problem is, the
> test suites in cvs are huge and will sometimes take hours to checko
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mary Lou RODRIGUEZ <[EMAIL PROTECTED]> writes:
> How can I edit the log description of the objects that have already been
> commited? Basically, some technical developers forgot to enter details
> during commit and I want to take note of the referenc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FCC <[EMAIL PROTECTED]> writes:
Be real here. You have a gmail account and still are playing games with
the reply address? Why do you make life difficult for everyone who might
want to reply to you?
> Anybody has any experience with such a setup?
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matt,
Matt Doar <[EMAIL PROTECTED]> writes:
> I understand how verifymsg can be used to check the text in a commit
> message. The problems is that I'd like to have different checks for
> different branches, and there is no "branch name" variable t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Denniston <[EMAIL PROTECTED]> writes:
> This reminds me of conversations held earlier in the list. I think
> several of them ended with something to the effect of 'putting the
> /tmp/ or LockDir which cvs uses on a RAM disk should make the whole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander <[EMAIL PROTECTED]> writes:
> > I only create the ,foo.c, file - I don't write anything into it; the
> > existence of the file is enough to act as the RCS lock; if I can do my
> > inplace modification then I delete this file after doing it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> * Paul Sander ([EMAIL PROTECTED]) wrote:
>
> Hi Paul,
> Thanks for the reply,
>
> > Everything that Mark says is true. I'll add that some shops optimize
> > their read operations under certain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> * Mark D. Baushke ([EMAIL PROTECTED]) wrote:
> Hi Mark,
> Thanks for your reply.
>
> > Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Alan Gilbert <[EMAIL PROTECTED]> writes:
> So - here are my questions/ideas - I'd appreciate comments to tell
> me whether I'm on the right lines:
> 1) As I understand it the tag data is the
> first of the 3 main data structures in the R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MoonsOfJupiter <[EMAIL PROTECTED]> writes:
> My command-line impared Mac-using workmates want
> to know what GUI CVS client they should be
> using. Some are using MacCVSX now. All are
> running panther.
>
> What do you think?
There a wide selection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tuong Tran Vu Ngoc <[EMAIL PROTECTED]> writes:
Note: Please do NOT send multipart/* or text/html MIME e-mail to the
info-cvs mailing list.
> I have read in a ebook called Open Source Development with CVS 3rd
> edition that we cannot use CVS as a serv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Weiss <[EMAIL PROTECTED]> writes:
> I've been asked to migrate our CVS repository
> over to Subversion (hope that's not a dirty word
> here).
Not at all. The svn community has lots of roots in CVS
and is considered by many to be a likely succe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Familie Moßner <[EMAIL PROTECTED]> writes:
> I'm faced with the requirement to trace changes due to certain bugfixes,
> i.e. to answer questions like "which files have been affected by change
> request 1234".
>
> Currently, the only way I can think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rajeev R <[EMAIL PROTECTED]> writes:
> I have already a cvs repository set up in our office .
> I am accessing the cvs repository using
> set cvsroot=:pserver:[EMAIL PROTECTED]:2401:/cvsrepository
>
> Could any one tell me THE STEPS to make this exi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Asselin <[EMAIL PROTECTED]> writes:
> Mark D. Baushke <[EMAIL PROTECTED]> wrote:
>
> > New imports are always on the vendor branch with -X and 1.2 is always
> > dead. So, the trunk is no longer ever potentiall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Asselin <[EMAIL PROTECTED]> writes:
> Mark D. Baushke <[EMAIL PROTECTED]> wrote:
>
> > Pierre Asselin <[EMAIL PROTECTED]> writes:
>
> > > ... It's important to understand that each
> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<[EMAIL PROTECTED]> writes:
> This has been talked about several times, so I said part 44! :)
>
> However something still does NOT make sense to me..
>
> My sandbox and server are BOTH on the EST time zone, at least when
> I say "date" I get the EST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
> [snip use-case]
> > This differers from your case where only a
> > portion of the repository is restricted.
>
> Interesting. Same idea, different subsect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop <[EMAIL PROTECTED]> writes:
> For us, an equivalent to the 'commitinfo' which
> runs at checkout-time would be very useful. The
> trigger would behave the same - an exit code of
> 0 allows the checkout to proceed, and a non-zero
> exit code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Asselin <[EMAIL PROTECTED]> writes:
> ... It's important to understand that each
> import after the first *breaks the trunk* until
> the merge has been successfully committed.
Note that if you are using cvs 1.12.x, you may
find the -X option t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hamilton, Mark E <[EMAIL PROTECTED]> writes:
> This is a multi-part message in MIME format.
Please do not send MIME encoded e-mail or text/html e-mail to the
info-cvs list.
> We just upgraded our SoureForge intallation,
> which included a CVS upgrad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guus Leeuw jr. <[EMAIL PROTECTED]> writes:
> > Have you considered moving to the CVSNT fork
> > of CVS? (Yes, it runs on boxes other than
> > Windows.)
>
> No, and I won't. I am a long time believer of CVS pure ;)
LOL. Okay. :-)
(I just hope you di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guus Leeuw jr. <[EMAIL PROTECTED]> writes:
> > > Hence I am looking at the pserver protocol, so I figured, it is a FAQ.
> > > Now depending how you interpret FAQ (asked or answered), I was right ;)
> > >
> > > It's apparently asked often, but
> > > ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guus Leeuw jr. <[EMAIL PROTECTED]> writes:
> Hence I am looking at the pserver protocol, so I figured, it is a FAQ.
> Now depending how you interpret FAQ (asked or answered), I was right ;)
>
> It's apparently asked often, but
> https://ccvs.cvshome.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Babcock <[EMAIL PROTECTED]> writes:
> On a shared webhost, my username is "[EMAIL PROTECTED]" and
> the hostname is "jimrandomh.org". With ssh, I can log in fine with
> "ssh -l '[EMAIL PROTECTED]' jimrandomh.org". However, I can't
> find a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods <[EMAIL PROTECTED]> writes:
> Yes -- we are in almost full agreement, but it cannot use '-n'. (no
> commitinfo scripts are run with '-n' and I don't think they should be or
> ever need to be)
I believe this statement does not reflect t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Captain Tantric <[EMAIL PROTECTED]> writes:
> This could be something I've done wrong, but am at a loss as to figure
> out a way around it. I'm running cvs 1.12.11 on Linux and have
> recently added the cvs_acls script to my commitinfo file. The cvs_a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> Is it possible to get some kind of overview of the CVS repository structure
> without using 3rd party tools like viewcvs?
cvs checkout -d -l top .
> I'm asking because if for example a user forgets the module he checked
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> Is it possible to give specific files / directories / modules specific
> user privileges? We need to be able to give people access priviledges
> to selective directories. Normally, one has access only to the
> component tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver Lehmann <[EMAIL PROTECTED]> writes:
> > If you are using a UNIX or Linux client, you
> > should be able to use:
> >
> >umask 077
> >cvs checkout module
> >
>
> The problem is, that it isn't generious 0700 some files are having other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver Lehmann <[EMAIL PROTECTED]> writes:
> I would like to use cvs with a group of users.
> That fact alone is quiet easy to handle by doing
> what https://ccvs.cvshome.org/fom/cache/92.html
> says. The problem I have is, that the files I
> want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander <[EMAIL PROTECTED]> writes:
> On Jan 30, 2005, at 10:24 PM, [EMAIL PROTECTED] wrote:
> > At present, it is clear from both sides that the 'cvs add' behavior is
> > broken. I have probably missed some of the points, but let me try to
> > su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander <[EMAIL PROTECTED]> writes:
> Wait a second. The "OK for addition, but wrong for commit" is exactly
> the status quo. The "cvs add" command succeeds, "cvs commit" fails
> due to commitinfo. What I'm proposing is "bad for addition, bad f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Greg,
Greg A. Woods <[EMAIL PROTECTED]> writes:
> [ On , January 21, 2005 at 20:06:37 (+0300), [EMAIL PROTECTED] wrote: ]
> > Subject: CVS diff and unknown files.
> >
> > Is there a way to include contents of "unknown" files into the 'cvs
> > diff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Jarvis <[EMAIL PROTECTED]> writes:
> I'm one of the CVS administrators here at my company (in addition to
> other duties of course), and I've been waiting for CVS 1.11.19 before
> upgrading all our users. I know there are some issues with 1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> I hate google groups. Had a whole thing typed out and ready to send and
> it failed, erasing all I had.
>
> Here's the skinny:
>
> SETUP:
> WinCVS 1.3.20.2 Beta 20 (Build 2) with CVSNT running on Windows 2000
> CVS 1.11.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Grand Poohbah <[EMAIL PROTECTED]> writes:
> I am setting up a FreeBSD 5.x machine with cvs 1.11.17.
>
> My goal is to have a "guest" style read-only access to a cvs repository
> under a strict chroot environment. I have setup my repository with fil
-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 paren
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jsWalter <[EMAIL PROTECTED]> writes:
> Is there a way to have a substitution happen only once?
>
> ie:
> I'm using phpDocumentor and would like to have the '@since' tag auto
> insert the CVS file version, but not change it the next time the file is
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> 2. Tell me what is YOYO. Is there is any special meaning for that?
There is no 'YOYO' in cvs to the best of my understanding.
More context is required if you want to track it down.
-- Mark
-BEGIN PGP SIGNATU
1 - 100 of 677 matches
Mail list logo
