On Fri, May 03, 2002 at 04:43:11PM -0400, Greg A. Woods wrote:
> [ On Friday, May 3, 2002 at 14:49:11 (-0500), Sean Hager wrote: ]
> > Subject: RE: merge mode for XML
> > > No. Not on extension, but based on *regular expressions*, or at least
> > > shell-style pattern matching expressions.
b_dompe <[EMAIL PROTECTED]> writes:
> This seems to work for existing files. However, when people try to
> add a new file to the repository, they get the error "cannot add file
> on non-branch tag ".
The error message is telling you what you need to know; read the CVS
manual about "branch".
>
> > > No. Not on extension, but based on *regular
> expressions*, or at least
> > > shell-style pattern matching expressions.
> Extensions are too
> > > simplistic. (c.f. CVSROOT/cvswrappers, CVSROOT/cvsignore)
> >
> > Extensions would work fine, pattern matching is overkill.
>
> Neit
[ On Friday, May 3, 2002 at 14:49:11 (-0500), Sean Hager wrote: ]
> Subject: RE: merge mode for XML
>
>
>
> > No. Not on extension, but based on *regular expressions*, or at least
> > shell-style pattern matching expressions. Extensions are too
> > simplistic. (c.f. CVSROOT/cvswrappe
On Fri, May 03, 2002 at 16:14:14 -0400, Greg A. Woods sent 0.8K bytes:
> [ On Friday, May 3, 2002 at 13:30:04 (-0400), Larry Jones wrote: ]
> > Subject: Re: Moving CVS repository
> >
> > Greg A. Woods writes:
> > >
> > > there are zillions of basically unsolvable issues which arise if there's
> >
[ On Friday, May 3, 2002 at 13:30:04 (-0400), Larry Jones wrote: ]
> Subject: Re: Moving CVS repository
>
> Greg A. Woods writes:
> >
> > there are zillions of basically unsolvable issues which arise if there's
> > any use of *info files.
>
> The way CVS handles a directory tree with multiple CV
> Yeah. That'd be a cool feature. But then, CVS will no longer be a
> standalone program. If you move the repository to another server
> where the modules are missing, how would you expect CVS to behave?
The plugins would be part of the module, so if you moved the module to
another CV
> No. Not on extension, but based on *regular expressions*, or at least
> shell-style pattern matching expressions. Extensions are too
> simplistic. (c.f. CVSROOT/cvswrappers, CVSROOT/cvsignore)
Extensions would work fine, pattern matching is overkill.
> Yes. Some mechanisms l
[ On Wednesday, May 1, 2002 at 13:33:08 (-0700), Glew, Andy wrote: ]
> Subject: RE: merge mode for XML
>
> Well, I wrote Perl-SQL, a relational database system that
> is self-schematizing - where every record can define its own schema,
> with its own fields.
Yeah, that sounds like something a per
[ On , May 2, 2002 at 09:33:45 (+0200), Lee Sau Dan wrote: ]
> Subject: Re: merge mode for XML
>
> > "Paul" == Paul Sander <[EMAIL PROTECTED]> writes:
>
> Paul> A better implementation would be to code a symbolic name for
> Paul> the merge tool in a newphrase in the admin section the
[ On Wednesday, May 1, 2002 at 07:23:23 (GMT), Ben Kial wrote: ]
> Subject: Any plan to merge cvspwd into cvs?
>
> I have been using "cvspwd" to manage my CVS user accounts in
> my :pserver host so that I don't have to create Unix accounts for
> each CVS user. However, "cvspwd" can only be execute
Greg A. Woods writes:
>
> there are zillions of basically unsolvable issues which arise if there's
> any use of *info files.
The way CVS handles a directory tree with multiple CVSROOTs is by
running the command once for each root with just the directories that
have that root. As far as I can te
Andreas Thalau writes:
>
> as I read on http://www.cvshome.org/docs/manual/cvs_2.html#SEC36 it is
> possible to gain read-only access to the repository for some users.
> I can´t find a hint on managing this for one repository based on
> modules.
You use filesystem permissions to control access t
On Thu, May 02, 2002 at 07:45:48PM -, b_dompe wrote:
> We bring a new tree up to date with the latest 'stamped' release by
> using "cvs update -r", where the release was created
> with "cvs tag -RF ".
>
> This seems to work for existing files. However, when people try to
> add a new file
On Tuesday, April 30, 2002, at 03:33 PM, [EMAIL PROTECTED] wrote:
> I have one config file that must exist in several directories in my
> project.
> I would like to be able to have CVS create this file in all its
> locations
> and still only have it stored once in the repository. Any idea ho
On Wednesday, May 1, 2002, at 02:36 PM, [EMAIL PROTECTED] wrote:
>
> We have all our source code in the CVS repository as
> one project. Now we want to start a new project in
> CVS. But we will be requiring files from the existing
> project into the new project. How can we copy/move the
> files
On Thu, May 02, 2002 at 06:25:54PM +0200, Stefan Bertels wrote:
> Case: I check in a file by accident and want it removed from the
> repository. But I need the file. Think of it as per-user options regarding
> to a project.
>
> When I call remove the local file will be removed at my machine now a
Laura Hopkins wrote:
>
> I'm trying to extract _all_ versions of a CVS file into a directory. Any
> ideas how to do this or whether it can be done?
The following will generate and run a script that will do the job:
cvs log $YOURFILE |awk '/^rev/ {print "cvs up -p -r" $2 " " rfile " > "
Danial Islam writes:
>
> In UNIX, if I had the repository and all the scripts set up in CVS
> 1.10, then if i start using the binary for CVS 1.11 during the middle
> of our code development, will my repository get screwed up?
No, they're upward compatible. Please check the NEWS file for chang
b_dompe wrote:
>
> Is there a way to check out only the directory
> even if it contains files?
No. What are you trying to accomplish by doing that?
> Alternatively, checking out the directory with just one specific file
> in it could be adapted to what we need. But we can't have it
> retrieve
On Thu, May 02, 2002 at 07:11:53AM -0700, Max wrote:
> I'm hoping to untangle a CVS hairball and need a good charting tool
> that will allow me to run against a repository and generate a diagram.
> Is there anything out there that already does this?
What kind of diagram do you want to ge
Hi,
I think this is a issue, that should be solved within your project and
its organisation (building, deployment etc).
Bye
Oliver
- Original Message -
From: "Karsten, Paul" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 01, 2002 12:33 AM
Subject: Sharing the same ph
22 matches
Mail list logo
