Along the lines of Andy Jones' "Tagging across branches" thread posted
earlier today, I have a similar question.
There have been many occasions in which I have wished it were possible to
have a module where some directories were on one branch, and some
directories were on another (and so on). I k
Fabian Cenedese writes:
>
> I know that the -l was removed from recent versions but I never created or
> changed a .cvsrc file. Can I prevent this error except by upgrading the
> cvs tools?
Only by not using the global -n and -R flags. They both imply -l but
the 1.12.1 client doesn't differentia
Andy Jones writes:
>
> I have a repository - that is, a subdirectory of $CVSROOT - which has
> a number of subdirectories.
Just a terminology clarification -- everything in $CVSROOT is a single
repository. Its subdirectories are "top-level directories" (or
"modules" although, strictly speaking,
Rolf Leggewie writes:
>
> $ CVS -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/noffle rlog ChangeLog
> CVS log: warning: the rlog command is deprecated
> CVS log: use the synonymous log command instead
Update your server -- the long-deprecated rlog alias for log was
replaced with a real rlog command i
Hi Larry,
thank you for the response.
[EMAIL PROTECTED] (Larry Jones) writes:
> Right, status requires a working directory. However, the rlog command
> does not require a working directory and it can also give you a list of
> tags for a file.
Well, here is what I got:
$ CVS -z3 -d:pserver:[EM
Hi Andy,
> From: [EMAIL PROTECTED] On Behalf Of Jim.Hyslop
>
> If they will be modifying the code, then your approach will not work. They
> will have to check out the branch tag for the legacy branch. You
> might want
> to write a simple script or batch file that will check out the appropriate
> d
Brandon Craig Rhodes' msg "How to run :gserver: nonroot", dated 03Jul2002,
closely describes our current situation: a brand new repository, with only
gssapi access, and no cvs user accounts on the respository. To recap, we
envision the repository server having only 2 user:group accounts:
cvsad
Thanks all and sorry again for this 'piece of cake!'
Thomas
Johnny Fulcrum wrote:
On Wed, 17 Mar 2004 17:53:16 +0100, Thomas Lavergne
<[EMAIL PROTECTED]> wrote:
Hi all and sorry if this seems a trivial issue : the faq is of no help.
I would like to checkout a release tagged version of my softwa
Hallo Thomas,
* On Wed, Mar 17, 2004 at 05:53:16PM +0100 Thomas Lavergne wrote:
> I would like to checkout a release tagged version of my software, but
> without all the 'CVS related stuff'.
You want to export your files, see "cvs export" at
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_16
On Wed, 17 Mar 2004 17:53:16 +0100, Thomas Lavergne
<[EMAIL PROTECTED]> wrote:
Hi all and sorry if this seems a trivial issue : the faq is of no help.
I would like to checkout a release tagged version of my software, but
without all the 'CVS related stuff'. I just want a directory with all my
I think you want the command 'cvs export' for the given tag. This does not
give you the CVS directories in the source tree. Stuff like $Id$ and $Log$
tags will remain in the sources though - it's not clear if this is what
you're referring too.
Other than that, I use 'cvs co foo' followed by a 'fin
Thomas Lavergne wrote:
> Hi all and sorry if this seems a trivial issue : the faq is
> of no help.
> I would like to checkout a release tagged version of my software, but
> without all the 'CVS related stuff'. I just want a directory
> with all my
> sources and makefiles in order to distribute
That would be "cvs export". You have to give it a tag or a date to export, but other
than that it's almost the same as "cvs checkout".
At 04:53 pm 17/3/04, Thomas Lavergne wrote:
>Hi all and sorry if this seems a trivial issue : the faq is of no help.
>I would like to checkout a release tagged v
"Jim.Hyslop" wrote:
>
> [EMAIL PROTECTED] wrote:
> > Todd Denniston writes:
> > > 5) is there a more efficient way of locking the repository
> > than creating all
> > > the `#cvs.rfl' in all the sub directories of all the
> > repositories? That is, is
> > > there a single file I can create that bl
Hi all and sorry if this seems a trivial issue : the faq is of no help.
I would like to checkout a release tagged version of my software, but
without all the 'CVS related stuff'. I just want a directory with all my
sources and makefiles in order to distribute it. I do not want copies to
contain
Andy Jones wrote:
> I have a repository - that is, a subdirectory of $CVSROOT -
> which has a number of subdirectories.
>
> For one of these subdirectories I have created a branch, and
> in my sandbox have checked out that branch. So in my sandbox
> I have the main trunk except for one directo
Hi all,
I have a repository - that is, a subdirectory of $CVSROOT - which has a number of
subdirectories.
For one of these subdirectories I have created a branch, and in my sandbox have
checked out that branch. So in my sandbox I have the main trunk except for one
directory, which is sticky o
[EMAIL PROTECTED] wrote:
> Todd Denniston writes:
> > 5) is there a more efficient way of locking the repository
> than creating all
> > the `#cvs.rfl' in all the sub directories of all the
> repositories? That is, is
> > there a single file I can create that blocks access to each
> repo for the
Hi
I'm quite sure I just read about this recently but I can't find a mail mentioning
it again.
We just set up a new repository and tried to work with it. Goes fine except
some errors I couldn't resolve yet.
Server: cvs 1.11.9
Client: cvs 1.12.1
(both Linux)
inetd.conf: cvspserver stream tcp nowa
19 matches
Mail list logo
