How can one remove a branch after merging it with the main branch ?
Thanks,
John
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
On Tue, 2002-10-15 at 17:33, John Noronha wrote:
How can one remove a branch after merging it with the main branch ?
There is no specific way that I am aware of to mark a branch 'closed' or
'not to be used anymore'.
If you really want to remove the historic record of the branch ever
having
Does anyone know what this means? I'm getting this message on a few files
when I do a checkout ..
It looks like the files in question are still available in the repository,
but they did not get checked out...
Thanks in advance for any help!
markl
All,
Feel free to disregard my previous e-mail (below). I answered my own question with
some experimentation. It looks like using alias modules with the -a flag and a
space-delimited list of paths will get me what I need.
Matt
-Original Message-
From: Matt Lyon
Sent: Monday, October
[ On Monday, October 14, 2002 at 16:32:20 (-0700), Anne McCaffrey wrote: ]
Subject: Re: Problems with Attic permissions
I have not invited any 'thoughts' or 'opinions' on how
I am using cvs.If you can't answer my question, pls
don't reply;we can go on arguing about the pros and
cons of
John Noronha writes:
Thanks for your help. The reason I'd like to remove the branch after merging
it with main branch is so that one doesn't inadvertently do a second
merge. Is there any way one can prevent this ? (other than ensuring that the
merged revision is tagged suitably).
You can
On Mon, Oct 14, 2002 at 10:02:17PM -0400, Paul Nicholson wrote:
'cvs -Qn rdiff -r 1.1 -r 1.2 -u module/file' fails with:
cvs [rdiff aborted]: cannot open /tmp/cvsyE7DIO: File exists
Using: CVS 1.11 (client/server)
That's ancient. Try upgrading. No guarantees, but many, many
bugs have been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for your replyI'll do that:)
~Paul
On Tuesday 15 October 2002 12:28 pm, Eric Siegerman scribbled:
On Mon, Oct 14, 2002 at 10:02:17PM -0400, Paul Nicholson wrote:
'cvs -Qn rdiff -r 1.1 -r 1.2 -u module/file' fails with:
cvs [rdiff
I'm trying
to use the export command to export files of a given revision, but am
unsuccessful. The command and options I ran is "cvs export -r 1.2 -d
testing testing123" and the error I get is "tag `1.2' must be a symbolic tag". If I create tags to represent the revisions and run
and "cvs
On Tue, 15 Oct 2002, Jason Yeung wrote:
I'm trying to use the export command to export files of a given revision,
but am unsuccessful. The command and options I ran is cvs export -r 1.2 -d
testing testing123 and the error I get is tag `1.2' must be a symbolic
tag. If I create tags to
Jason Yeung writes:
MIME-Version: 1.0
Content-Type: multipart/alternative;
Please do not post MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
I'm trying to use the export command to export files of a given
revision, but am unsuccessful. The command and options I
can use -r HEAD which will export the head revision
of each file. You might be able to use the -D option to export as of a
given date for what you need.
Note that -D can take many formats, such as
20021015
2002-10-15
now
today
yesterday
20021015 10:15:00
Also note that if you enter
[ On Tuesday, October 15, 2002 at 14:15:41 (-0700), Jason Yeung wrote: ]
Subject: Exporting file versions
Because my project has a lot of files, creating tags for each version of a
file would be very tedious. I was wondering if there's a way to export files
without creating tags? If you need
We're switching to pserver but one of our developers is having problems
committing changes from the top level. I realize that Template is
copied to the CVS directory in each subdirectory and commits in those directories
work fine. I set TopLevelAdmin=yes in CVSROOT/config but the CVS
directory
14 matches
Mail list logo
