The following command builds cvs-1.11.9, but not cvs-1.11.10 under
windows:
nmake /f cvsnt.mak CFG="cvsnt - Win32 Debug"
The failure appears to be:
link.exe @c:\temp\nma01012.
filesubr.obj : error LNK2001: unresolved external symbol _assert
.\WinDebug/cvs.exe : fatal error LNK1120: 1
I would like to run all commits of .h and .cc files through a pretty
printer to automatically assist in later merges and conformance to
style. I'm running a pserver. Are there any tips I should know of
how to do this before trying?
Thanks,
Dave.
___
On Thu, Oct 02, 2003 at 03:32:43PM MDT, Derek Robert Price wrote:
> ~From the NEWS file:
>
> | Changes from 1.11.6 to 1.11.7:
>
>
> . . .
>
> | * The global '-l' option, which suppressed history logging, has been
> removed
> | from both client and server.
DOH!! I read that but didn't put two
Using pserver cvs-1.11.7 on solaris and client cvs-1.11.6 for aix,
hpux, or solaris, there is this problem which does not occur when
the client and server are the same version:
cvs release -d example
Protocol error: bad global option -l
cvs release: unable to release `example'
Thanks,
Dave.
__
Thanks Larry! This fixed it.
--- Begin Message ---
David Everly writes:
>
> All three have the same behavior of showing the password (which was
> not present with 1.11.6). Output of "uname -a":
>
>AIX chanegw0 3 4 000110554C00
>SunOS ndccsr02 5.8 Generi
On Tue, Sep 30, 2003 at 03:10:08PM MDT, Larry Jones wrote:
> David Everly writes:
> >
> > (Password is not displayed while typing it, but is displayed after
> > pressing the ENTER key.)
>
> On what platform?
>
> -Larry Jones
All three have the same behavior o
Under cvs-1.11.7, the password is displayed on the client screen
as follows:
cvs login
(Password is not displayed while typing it, but is displayed after
pressing the ENTER key.)
I know pserver in general is not very secure, but is there any
way to have a patch or fix that might eliminate this d
On Tue, Mar 25, 2003 at 10:21:55AM MST, Brian G. Peterson wrote:
> If your Windows 2000 client is using FAT or FAT32 as the filesystem, then
> no, because the internal representation of the filename is case insensitive,
> and stored as all upper. If the filesystem is NTFS, it should work.
The win
Our cvs pserver is on Solaris. A cvs client is on windows 2000.
We are using the latest version for both server and client.
Initially, we had a directory in all uppercase (SOMEDIRECTORY). We
did cvs remove -f of all the files in that directory followed by cvs
commit. Then we made a different di
On Fri, Jan 17, 2003 at 10:03:06AM MST, [EMAIL PROTECTED] wrote:
> Do users connecting using the pserver method need a real account (shell
> login, home directory,...) on the machine running cvs pserver?
No, search for "passwd" in the following:
http://www.cvshome.org/docs/manual/cvs_2.html
_
On Fri, Jan 17, 2003 at 10:03:06AM MST, [EMAIL PROTECTED] wrote:
> Do users connecting using the pserver method need a real account (shell
> login, home directory,...) on the machine running cvs pserver?
No, search for "passwd" in the following:
http://www.cvshome.org/docs/manual/cvs_2.html
__
On Wed, Jan 15, 2003 at 10:04:43AM MST, [EMAIL PROTECTED] wrote:
> From: "Markel, Ryan" <[EMAIL PROTECTED]>
> Subject: CVS Server step-by-step?
>
> I'm trying to set up a repository currently on our school's Debian 3.0r1 =
> box,
> which currently has the Debian packacge for CVS 1.11.1p1 installed.
My developers sometimes ftp text files as binary from windows to a
unix machine and then commit these files to cvs.
I have these files defined in cvswrappers as:
-k 'o'
Some other files are defined in cvswrappers as:
-k 'b'
In my commitinfo script, how do I discover if the file is marked
-k
No, thank you. :)
On Wed, Jun 26, 2002 at 04:21:11PM -0400, Larry Jones wrote:
> David Everly writes:
> >
> >cvs tag -c MY_TAG
> >cvs server: someFile is no longer in the repository
> >cvs server: someFile is locally modified
> >cvs [server a
It seems to me that I'm getting unexpected behavior in the following
scenario (in order of occurance):
me in my workspace:
cvs commit -m "commit of everything in my workspace"
someone else in a different workspace:
cvs remove -f someFile
cvs commit -m "removing someFile from the repo
No issues beyond the ones documented at:
http://www.cvshome.org/docs/manual/
specifically:
http://www.cvshome.org/docs/manual/cvs_2.html#SEC29
On Mon, Apr 22, 2002 at 02:55:49PM -0400, Matt Riechers wrote:
> David Everly wrote:
> >
> > Does using a "pserver unix clie
Does using a "pserver unix client" which access the "pserver unix server"
on the same machine as the client cause any problems other than those
which are normally encountered using "pserver unix client" to access
the "pserver unix server" on a remote machine?
--
[EMAIL PROTECTED]
V-Net: 622
Is there some technique I can use to prevent my developers from
directly altering the cvs repository and force them to use cvs
commands instead?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
On Thu, Feb 28, 2002 at 02:22:13PM -0800, Paul Sander wrote:
> In other words, others have committed to your target branch before you
> finished resolving conflicts and committed your work, right?
>
Yes.
> What exactly do you want to do in that situation? Do you want to update
> to the top of
How do I commit a large number of changes (generated by a merge) to
the branch I'm merging to when there are several commits to that
branch while I'm in the process of merging? And if I do update before
commiting the merge (to bring in the new changes so that I'm allowed
to check in) is there a w
We currently have 3 active development branches as well as our trunk.
Our trunk holds our next major release. Branches A, B, and C hold our
next three major releases (in that order). About once a week, we merge
the incremental changes (since the last merge) from the trunk, to branch
A, then from
In my cvs project, I want tags to never change once they are applied.
However, after adding new files, if someone applies a tag that has
already been used to the project, the tag is applied to the new files.
How can I prevent this?
___
Info-cvs mailing
I have an unusual situation:
My project has the following tags (in order of appearance):
tag_a
tag_b
tag_c
I have been asked to see if I can take the project back to tag_b and
then add in the changes made between tag_c and now.
So I did the following to see what would happen:
cvs checkout my_
I have the latest cgi script from http://www.idaemons.org/~knu/cvsweb/
and am running it with cvs 1.11.1p1 and rcs 5.7 on sun solaris 2.8
with iplanet enterprise server 6.0SP1.
Everything seems to work (including annotate), with the exception of
clicking on a revision or download link. When acce
ones wrote:
> David Everly writes:
> >
> > I have text files, but they should never be merged.
>
> Then why are you using CVS?
>
> > Should I then use
> >
> > * -k 'o' -m 'COPY'
> >
> > or should I use
> >
> >
Please disregard this, I think I fat-fingered something here, because
now it works for me the way I think it should.
On Mon, Dec 03, 2001 at 11:09:02AM -0700, David Everly wrote:
> I have branch MY_BRANCH and HEAD development. There have been fixes
> to HEAD and new development that do
I have branch MY_BRANCH and HEAD development. There have been fixes
to HEAD and new development that does not have these fixes on
MY_BRANCH. It seems that the fixes to HEAD are not retained when, in
my HEAD work area, I do cvs update -j MY_BRANCH. Instead, files which
seem to have not changed r
I'm struggling to know what to put in cvswrappers:
I have text files, but they should never be merged. Should I then
use
* -k 'o' -m 'COPY'
or should I use
* -k 'b' -m 'COPY'
and does the -m 'COPY' actually have an effect?
The files have already been checked in, so how do I use cvs admin to
I don't like moving or deleting tags, so I have the following taginfo
script:
#!/bin/sh
##
## do not allow anyone to move or delete tags
##
if [ $2 = "mov" ] ; then
echo "--->Please do not try to move or change existing tags."
exit 1
fi
if [ $2 = "del" ] ; then
echo "--->Please do not
Thanks...this fixed it...
On Thu, Nov 29, 2001 at 04:12:05PM -0800, Paul Sander wrote:
> Have you looked into using -ko for this purpose?
>
> --- Forwarded mail from [EMAIL PROTECTED]
>
> By the way, the reason I'm using -k 'b' is so that there is no
> substitutionbut these should be all me
My cvswrappers has:
* -k 'b'
Then I started getting cvs update: nonmergeable file needs merge.
So I tried:
* -k 'b' -m 'MERGE'
However, the problem still happens...possibly because all the files
were checked in on the earlier configuration.
What is the setting I really want here, and how do
By the way, the reason I'm using -k 'b' is so that there is no
substitutionbut these should be all mergeable text files.
On Thu, Nov 29, 2001 at 04:12:18PM -0700, David Everly wrote:
> My cvswrappers has:
>
> * -k 'b'
>
> Then I started getting c
I ran the following on a copy of my pvcs archives:
pvcs2cvs.pl -r flat -p flat
Then copied all the *,v files into a cvs root directory which I then
did 'cvs init' on. Should I have taken a different approach here?
There was a pvcs floating label which originally was defined as 1.*
which got co
Since I didn't see any responses, I thought I would ask this once
more:
How can I keep users from doing 'cvs tag -b' and still allow 'cvs tag'
I'm aware of CVSROOT/taginfo, but I don't see any arguments that
indicate whether it will create a branch or not.
$2 only has 'add', 'mov', 'del'.
Is GNU expr required for CVS or only for the 'make check' testing of
CVS?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
To recap, I'm looking to a way to lock branches so that people don't
accidentaly check out or commit to an 'inactive' branch. I also need
the solution to work for those accessing CVSROOT vi the :ext: method.
cvs -n stat filename seems only to work from a 'sandbox' point of
view. How would I use
I'm thinking that what I do works to not allow tag changes:
First, I define a 'cvsadmin' group.
Second, I place this line in $CVSROOT/CVSROOT/taginfo:
ALL $CVSROOT/CVSROOT/tagrules.sh
Third, I place tagrules.sh in my $CVSROOT/CVSROOT/checkoutlist
Fourth, my tagrules.sh looks like this:
#!/bin
Yes, this might work...I was also thinking maybe read/write locks for
branches, just in case the branches ever needed to be 're-activated'.
On Tue, Oct 09, 2001 at 04:22:58PM -0400, Eric Siegerman wrote:
> On Wed, Oct 03, 2001 at 12:18:23PM -0600, David Everly wrote:
> > Aft
How can I keep users from doing 'cvs tag -b'?
I'm aware of CVSROOT/taginfo, but I don't see any arguments that
indicate whether it will create a branch or not.
$2 only has 'add', 'mov', 'del'.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gn
Hello,
After I merge a branch into the trunk, I would like to make it so that
people cannot commit to the branch anymore. Would someone please suggest
a good way of doing this?
Thanks,
Dave.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu
If I understand what you are trying to do, prehaps this will answer:
http://www.cvshome.org/docs/manual/cvs_18.html#SEC171
On Tue, Oct 02, 2001 at 07:11:06PM +0200, raptor wrote:
> hi,
>
> I'm tring a loginfo-script.. and I got lock problems..
> OK first I expected that 'cause the cvs-commit is
My department is looking to purchase commercial support for CVS. Does
anyone do that? If so, who?
Thanks,
Dave.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
42 matches
Mail list logo
