something else is the bottle neck unless every one of
them are waiting for read or write locks in the repository.
You may wish to look into using a memory filesystem on the box along
with a LockDir directive in your CVSROOT/config file to point to it.
Good luck,
-- Mark
-BEGIN PGP
,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFC1oI13x41pRYZE/gRApo6AJ9zqXNHVqB3B4bwrIc/LYfpCYhR5gCg5qIf
ib/e0gF8/2ONr/ZU9xEl1io=
=oIL3
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs@gnu.org
http
into the contrib directory.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFC09RL3x41pRYZE/gRAvQTAJ47rUWCpBSQgvZYbr7AYCTSSWyhEACdEnlg
UYTLDEpkhu9yM4Uue57ZvXs=
=lAGA
-END PGP SIGNATURE
and always return true. This
will stop any warnings that cvs 1.12.x might want to give you for using
the older style format string defaults.
As always, it is recommened that you run tests on a repository other
than your main repository to be sure you understand how things work.
-- Mark
mdb
of commitinfo, verifymsg, loginfo scripts being used (if any)
is desirable.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCzM+U3x41pRYZE/gRAuJCAKCqSqL/4wjCV3QoR45oAIuDgMyVsgCfQ/Wi
jXrtVnZZQE1vvlDu/87VN54=
=tfWn
-END PGP SIGNATURE
when it fails?
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCzNdK3x41pRYZE/gRAltnAJ9iOe0I8ZJT9bC6pGq+0TNhwFhkXQCfTXyu
VFeqwMKzQNKl4zP13Bau2B8=
=VNoE
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs
/null
project2 (chgrp -Rf project2 /usr/local/cvsroot/project2; cat) /dev/null
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCzN/e3x41pRYZE/gRAmr0AJ9s5/DMr7yEYugqRlp61oxQN8+5KACg0T9J
0064dezA7A87GjCC6NX3BV0=
=gcll
-END PGP SIGNATURE
of the manual:
https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC175
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http
you many problems
otherwise as that release of CVS assumes a C89 capable standalone
compiler.
Does the following patch fix your problem?
-- Mark
ChangeLog entry:
2005-07-06 Mark D. Baushke [EMAIL PROTECTED]
* getpass.c (getpass): Add a KR style function definition.
Index
the groupid of the
parent directory. A crontab job could go thru and change the ownership
of the files and directories in the tree to that of the 'cvs' user on a
periodic basis as additional cleanup if desired.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD
-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 owned by him, not
by the global cvs user, and nobody
that runs on FreeBSD? I only see versions for
other Unix platforms, just nothing that explicitly says FreeBSD. Can
anyone help?
Just use /usr/bin/cvs as found on all FreeBSD distributions.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCwYII3x41pRYZE
.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCwYGL3x41pRYZE/gRAoSFAJ0Ts8xVnDH/P9xcGDrmuJnk+nwKCACgtfYg
9MwrS9kbAwYzGDsrgSiBPqE=
=AdTT
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs@gnu.org
http
-ssh-cvs-server.en.html
http://www.prima.eu.org/tobez/cvs-howto.html
http://www.informatimago.com/linux/chrooted-ssh-cvs.html
You may also find other documentions via your favorite search engine.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD
to manage a
system like that. ;) ) The only issues are those that always come with a
large UNIX/LINUX system; managing user accounts, storage, and backups,
and these are all people and resources issues, not technical issues.
Regards
Jain Pars
-Original Message-
From: Mark E. Hamilton
://lists.gnu.org/mailman/listinfo/info-cvs
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
system
or you would need to use the -d option on the command line. Check the
script to see if it is setting those variables. If the script is running as
a different user I guess it's also possible it might be using a different
environment, too, but given Windows I doubt that is the case.
-Mark
file was okay. If not, then use cvs2cl or
some other logging tool to get the dates into a file for you to consult.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCpx193x41pRYZE/gRAnidAKDWTiPhcM0c/TPrcDh4F+uAYIs0GQCfQwgI
loShhKqujYoorYF6F4ll9Bk=
=6X2O
-END
methodology is up to each project admin(s). However, if
they're using CVS correctly the stable and development revisions should
reside in the same repository, with the Stable revision(s) tagged and
branched.
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia
Would it be possible to reduce the re-attempt interval after cvs
encounters a lock to 15 or even 10 seconds, or maybe a configurable
build option?
Reason I'm asking is that we have cvs triggers that interact with a
separate repository. Sometimes commits to the repository can be held
up when
the subject line
that you desire and is passed the %p and %{sVv} arguments separately.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCo9Nq3x41pRYZE/gRAqqLAJ9gjvisomA3Dx4sJNJMTyVavAmnbACgpL7v
osF2nAmJX7sxOAgahOP5iCY=
=OcfP
-END PGP SIGNATURE
You have to be able to access the CVSROOT even for an add. The server will
check to see if the file was previously deleted and if so retrieve it from
the attic. Also, if the file were in a new directory the directory would be
added to the repository. In general you should expect most cvs
the job. If you have problems, contact the project folks
for that project on sf.net.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCn04R3x41pRYZE/gRAopbAKC2Bpywn4GIftSQVGPnjouEy0dlVgCgqTd1
RaT2Fn/8knJU4C1vYKr4Pe0=
=qj1Y
-END PGP SIGNATURE
: use 'cvs commit' to add this file permanently
% cat test7.dat
Test Message.
Test Message.
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
Adapt cvs_acls to your needs or write your own commitinfo trigger
script.
Documentation:
https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.html?rev=HEADcontent-type=text/html
Source:
https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in
Enjoy!
-- Mark
out
fairly easily using PERL or sed or awk ... depending on what else your
script needs to do.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCk1A/3x41pRYZE/gRArBUAJ9tGEwhkYK9FgjIw90uXaxYZL6PTQCfTndr
QJP8brRTGTZglpMCgZzwzHs=
=fAYC
-END
that that version of cvs did not have anything
going by the name 'Case' in it.
-- Mark
pginfo [EMAIL PROTECTED] writes:
Hi all.
We are using cvs from long time (it is great software, thank you!).
At the beginning we installed cvs server (v. 1.11) on linux mandrake
and it is working till
.
If you want more help, you should probably try capturing the output of
the conifgure command itself.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCkbRj3x41pRYZE/gRAhmPAJ9Race+CzD7HPeclqhJfMkQoDiUsACcDMdi
5DkdlCaRFNo5FzlTi5SOZVo=
=Cd0P
Rondal,
Mark E. Hamilton wrote:
Rondal,
5. Now you can start the remove/test cycle that Todd suggests, with the
assistance of a Senior Developer.
BTW, don't lose the test script/program that you use to validate that
the production area is still working. In fact, you should commit
goes here the system asks them to
provide a brief comment, however, this can easily be bypassed.
Can a template be set up or is there anyway to do this through the
Admin level?
Yes.
Read https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC178
-- Mark
-BEGIN PGP SIGNATURE
compatible in the cvs 1.11.x STABLE release line.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCiw2P3x41pRYZE/gRAvfAAKDCIakNLDmwBclaRO3Olnqd8cn4LACgjJvD
lBvKKxJrnWT+nFoTDgjXUhQ=
=TdJA
-END PGP SIGNATURE
repository and run the 'cvs init' command to see
what it does to your test setup before you do the real thing.
Good luck,
-- Mark
It does appear that one needs to check a backup in order to be sure since
the full context of the cvs init operation is not known.
I suppose
systems (eg, something like 'find $CVSROOT -type d -exec chmod+s {} \;')
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCi5xT3x41pRYZE/gRAsTeAJ9lRduWE9hXpcywqjMD+Qwf4imjDACfSoiU
mKnYLGoG9wJC06jpyZc15U0=
=Pg6U
-END PGP SIGNATURE
the Admin
level?
You can use the verifymsg administrative file to validate the log
message prior to commits.
https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC172
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666
://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in?rev=HEAD
You may find searching lists.gnu.org useful. Here is an interesting thread:
http://lists.gnu.org/archive/html/cvs-utils/2004-02/msg00047.html
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCg6Fm3x41pRYZE/gRAuxRAKCSZGcNNmuYTfsgtF+dAU4hnybqbwCdF+Cv
3wY0YVrrgAx85rq+tt33Bo0=
=2sJB
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs@gnu.org
-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
-1.11.20/cvs_18.html#SEC184
If you see that you are indeed configured to use
TopLevelAdmin=yes, then Arno Schuring's analysis
that you are unable to create and populate a
C:\CVS directory is likely the root-cause of your
problem.
Good luck,
-- Mark
Steve
Original Message
#my comment: looks like it checks it
out though anyway it just likes to complain...
...
and so on and so forth about every file that already exists.
This would seem to indicate a problem with the case of your file names.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3
, the pre-* and post-* tags are not necessary.
I urge you to one of the fine books on cvs (cf,
https://cvsbook.red-bean.com/) to help you understand the subtle points...
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCgml73x41pRYZE/gRArtIAJ0S3hx1
be monitored by
anyone. Maybe they will learn something.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCgEvd3x41pRYZE/gRAowSAJ9TUzwwn72yDamUyivjn3t04MNAhgCgy1ps
/5a/xVDtRPac0L1C9oGD9Y8=
=Z/a1
-END PGP SIGNATURE
has been exported into the
environment, you may wish to use the 'printenv' command:
printenv CVS_RSH
Or, you could have your 'echo' command inside of a shell script that you
run.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCgPeY3x41pRYZE
'Client: Concurrent Versions System (CVS) 1.11.20 (client/server)'
'Server: Concurrent Versions System (CVS) 1.11.20 (client/server)'
or whatever version is actually running on the client and the server.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD
is still used by employees of
their company. It makes the company look bad to
arbitrarily add such text to outgoing e-mail...
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCewkp3x41pRYZE/gRAhVnAJ9uwoLED4Ver7Iiv5PdZNUAucGV+wCglZeD
X+2WpFdBykbA5Fv/bpCf51E=
=J
the module
Validator commits the module in CVS
I suggest you look into using Aegis *http://aegis.sourceforge.net/)
which is a transaction-based SCM system that addresses your described
needs.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCe5hQ3x41pRYZE
of CVS dependencies.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCeTyt3x41pRYZE/gRAmqzAJ9Pmh1nY1u3hRQ7sVkQERT+zZNvfwCeJtPB
CoMpi1tQXL3DCIzvk587W7w=
=DZ1B
-END PGP SIGNATURE-
___
Info-cvs
: Arthur Barrett [EMAIL PROTECTED]
cc: Conrad T. Pino [EMAIL PROTECTED], HSP [EMAIL PROTECTED],
info-cvs@gnu.org
Subject: Re: Question about binary distribution
In-Reply-To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
From: Mark D. Baushke [EMAIL PROTECTED]
X-Mailer: MH-E 7.82+cvs; nmh
template being used.
Be advised that specifying /tmp for a critical file
is probably not wise. You may wish to put that file
into the CVSROOT directory itself.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCeTvf3x41pRYZE
of the numerous books
on the subject?
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCdFhh3x41pRYZE/gRApbQAKCQI93/g8U4/DwnbdlJlFO1jcJY1gCdHGJC
MIEltu2zufd/dS721yZPyTs=
=J2/w
-END PGP SIGNATURE-
___
Info-cvs
to ask questions about the
TortoiseCVS or WinCVS you are likely using and how it works with ssh.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCcTLZ3x41pRYZE/gRAjzQAJ9nj7u7n7a0LXhCUpEngK1WykzaBACfT7tM
PVbhTdjysm9psZiw/8Ow1K0=
=5Wtj
-END PGP
a cvs
process. However, installing the software does not require that you
actually run cvs, so do whatever you feel comfortable doing.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCcWDY3x41pRYZE/gRAne4AJ95qOxWynPPX4cWt0zQ/9z/pzI9iACfVDyf
and therefore their own
$HOME/.ssh/authorized_keys file. Then have them use the :ext: protocol
with CVS_RSH=ssh so that they use cvs over ssh.
You may want to use google to find out how to do restricted shells if
you do not wish to grant general user login capabilities to those users.
-- Mark
(eg, 'gmail.com' or 'hotmail.com')
and use that for futher communications with info-cvs@gnu.org to avoid
trying to place any restrictions on the dissemination of your e-mail.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCb9g73x41pRYZE
need to worry about
the filesystem under the mount point as well.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCZ4/M3x41pRYZE/gRAmspAJ9ajMxiwPryxfEb/gkAk2pJNmyJHgCfeMJp
3bzThg7d9qmxS84vjgMcSOM=
=GAB2
-END PGP SIGNATURE
-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 cvs version is 1.11.20 and after updating my system, I started
-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:
I was using CVS in local machine fine; running on top of Fedore Core 4.
my
/html/info-cvs/2005-02/msg00274.html
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCaDoo3x41pRYZE/gRAlcqAJ966uy7a8wTL6mxli4FVYptRI+EggCfbGWw
mwntH1fZ3+5SFmQTCS7tLHk=
=mjIK
-END PGP SIGNATURE
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCX+F83x41pRYZE/gRAocBAKCNSsYxh/rMReoB6XNjfEuMuGLwAQCgy6cw
E3xH5T7n8XGU9p+A3zjyjCg=
=CthY
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info
[EMAIL PROTECTED] wrote:
I have a text file that, for some reason, has a -kb sticky option.
How do I clear it via cvs admin?
cvs admin -kkv file.txt
cvs update -A file.txt
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
, it will clear the sticky tag. However, you can do
cvs update -A -r b_branch Makefile
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http
[EMAIL PROTECTED] wrote:
So the sequence is then...
cvs admin -kkv Makefile
cvs up -A -r b_branch Makefile
Correct?
Yes.
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
= product branch B
No.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCXVuq3x41pRYZE/gRAjCnAKCbKqbJ8xvb6tTPO9sGoF31oZACIwCcCpAD
5w8tDH+ShgFhCsPkxXMmWD4=
=DqQm
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs
of the modules
file unless you replaced the version on the trunk.
-- Mark
Would be cool to allow definition of modules per branches :)
Thanks again for your answer,
JP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Pierre Sevigny [EMAIL PROTECTED] writes:
Modules are cool
cvs rtag: Tagging test1
cvs rtag: Ignoring test1/test2
sahp6613% cvs rtag test_tag2 mod_test2
cvs rtag: Tagging test1
cvs rtag: Tagging test1/test2
cvs rtag: Tagging test1/test2/rtest
cvs rtag: Tagging test1/test2/rtest/null
cvs rtag: Tagging test1/test2/rtest/null/a
--
Mark E
Doh! I left out a really important '!'. Sorry. Your module should be:
mymodule -a !Project/Web/Clientx Project/Web
(See section C.1.4 of Cederqvist for a little more info. ;)
Mark E. Hamilton wrote:
Jean-Pierre,
Jean-Pierre Sevigny wrote:
Hi,
I have a module, say mymodule, defined like
for history.txt,v, instead I found a new file
history.txt was located at secondary repository there which already
contain latest change in this file.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCUj933x41pRYZE/gRAji/AJ4sExGfquzTXS
(Sasken) unless sent with that express intent and with due
authority of Sasken. Sasken has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for
any damage caused by any virus transmitted by this email
-- Mark
-BEGIN PGP SIGNATURE
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCU26x3x41pRYZE/gRAnLRAJ9r9JPwpcRANp6jfIDu6DSS22fwfQCfXLDl
/DWMS1HlzLIGaLjphAummwM=
=nQdK
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs
Is there any reason not to use the -n option to cvs when calling rlog?
Is there a way to run rlog without getting the comment entries in the output?
Thanks,
Mark
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info
to the various CVSROOT trigger files.
Read
https://www.cvshome.org/docs/manual/cvs-1.12.11/cvs_18.html#IDX319
for more details.
(I believe this feature was introduced in cvs 1.12.6.)
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCTsoU3x41pRYZE/gRAqPaAKC
the notion of a read only mirror repo?
Thanks in advance for any info.
Mark Lancisi
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
a consistent set of configuration files for commits.
Note that info-cvs@gnu.org is not really about CVSNT questions, so you
probably want to look into http://www.cvsnt.org/ for more answers.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCSu4U3x41pRYZE/gRArknAJ4
for details.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFCS1Hx3x41pRYZE/gRAq4OAJ0Q2OIo6ekBGiHt4Ct/5E9ZNT6vQACfarA1
KM2J1OqTkt3rnpKCtcKJ8aY=
=pRdd
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs
once the branch is known
might work. Bit hokey though.
Environment: cvs server 1.12.9, older clients and SmartCVS 4.0
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCQyWD3x41pRYZE/gRAoArAJ94H8pi/XmNXot3KWfNV7C8GLJpqQCg4KnR
1tStJr/FWDqKh97o84h/qOQ=
=n10P
will likely find changes considered for inclusion in future versions of
CVS.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCPvBl3x41pRYZE/gRAk3eAJ0ageE1b5X67SuvqubxXKXHUPHjIACgikBw
Muqs+EjIyczfddfr7EZT8Aw=
=2X8W
-END PGP SIGNATURE
of the branching
information outside of the RCS files already.
See http://users.footprints.net/~kaz/mcvs.html
for more details on Meta-CVS.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCPaS23x41pRYZE/gRAjULAJ9RzLHw+gUDoMCbF0zjgmStBJIT9gCfUU83
-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:
So - here are my questions/ideas - I'd appreciate comments
-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
!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCPnkr3x41pRYZE/gRAtu0AJ4qNbP4WSN9C60hZsaBejYwYcbnDACdGsOZ
RMw/SnkdG/mGOP2oyrdWnis=
=lD1h
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs@gnu.org
http
Hello -
I've got a branch that was branched some months ago from the trunk of one of my
projects.
I'd like to diff the head of this branch with the HEAD of the trunk.
So - while in the top level directory of a local checked out copy of the branch
I run:
cvs diff -rHEAD
Problem is, this
that you consider whether this
convention is really doing what you want it to do, and is worth adhering to.
Mark E. Hamilton wrote:
Is this in fact a typo, or is there some other meaning/use for this
`name' pattern?
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia
for this
`name' pattern?
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
on Window Platform? (only
client)
Is it right?
Yes. You probably want to use the CVSNT (see http://cvsnt.org/) fork of
CVS which has support for being a server on a Windows Platform.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD
like using GNU Emacs plus
/usr/bin/cvs as the interface.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCMVxy3x41pRYZE/gRAnOFAKCjWqn1MAs2pja7a9czxLn0cLVgHgCfbjLT
DOo2SD5fGvcodoV67OA5+p8=
=wEms
-END PGP SIGNATURE
3 - Run a sanity checking application that I've yet to find :)
You probably wan this tool:
https://ccvs.cvshome.org/source/browse/ccvs/contrib/validate_repo.in
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCMOBj3x41pRYZE/gRAojdAJ9f
), but when I type
^test
in bash I get the same error
-bash: :s^test: substitution failed
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http
way to your own
applications.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCKyEb3x41pRYZE/gRAqHgAJ401IbLhaxuvmhAu49ftt7zuYd9QQCggYUp
08L2n1P3Qe686QoQ/ZxlJbo=
=pUS6
-END PGP SIGNATURE
Another option is to install Cygwin and use the cvs server that is part of
Cygwin. Cygwin also has lots of other goodies from the Unix world like an
ssh server, grep, tail, etc.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
alexx
Sent: Thursday, March
Swaroop,
It is not clear from your message why you need to use the rcs version
numbers. If you are already using tags then you seem to have missed the
point of why they are useful. I can't imagine a reason why you couldn't
just tell somebody the tag name and have that be good enough. Maybe I
.
Most folks also use Apache for this purpose. You may wish to ask the
http://cvsnt.org folks about using Microsoft IIS.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCIqCk3x41pRYZE/gRAsYaAKC5fSK+VztekHzayw3GknsmYREo0ACffttx
kdFQD3o+NjE/w1mkGFDcTqY=
=PEqq
-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 potentially broken.
Hmmm, I see. I had read
with adding a
checkout trigger. It suppose it might let cvs
administrators 'hide' things in CVSROOT more
effectively if there is a need to do that.
Thanks,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCHLzg3x41pRYZE/gRArYrAJ97FuPuEVj/kKqP3mcoaEgnwdyJ
-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 subsections
(as you say, an inverse of our
,
but it's set to EST correct?
CVS keeps time in UTC to allow for clients that may be in other
timezones. It is always in UTC. User input of dates defaults to
local time, but you may add a timezone explicitly to the datestamp
if you wish.
Enjoy!
-- Mark
-BEGIN PGP SIGNATURE-
Version
-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
import after the first *breaks the trunk* until
the merge has been
to be of interest as it does
NOT put an import branch into the mainline
directly. Instead, a dead version 1.2 is created
on the first import.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCGtMv3x41pRYZE/gRAs11AJ94HYsp48nas1swaZuQhRcZg8DQxgCgnNr8
EMkWobH0Bct7dwMp
checkout: Updating test1/rtest
(which is what used to be output when doing local repository updates.)
This is not a problem, but I want to be sure that it is not indicative of some sort of build or configuration error on our server.
--
Mark E. Hamilton
Orion International
-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 upgrade
the repository file could be corrupted, so that this wouldn't work?
--
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
844-7666
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman
Spiro Trikaliotis wrote:
If you are working from Unix boxes solely, this works as expected. If
not, chances are you have to check in a new binary file.
You mean that there are other computers besides Unix-like systems? ;)
Thanks.
--
Mark E. Hamilton
Orion International
1 - 100 of 985 matches
Mail list logo
