I had a similar problem and was about to post. It's like somebody magically
read my mind. Thanks Christian for posting and many thanks Pierre for the
solution. :)
Steven
----Original Message Follows----
From: [EMAIL PROTECTED] (Pierre Asselin)
To: [email protected]
Subject: Re: How to "undo" a commit?
Date: Sun, 22 May 2005 00:00:28 +0000 (UTC)
Received: from lists.gnu.org ([199.232.76.165]) by mc2-f12.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211); Sat, 21 May 2005 17:04:11 -0700
Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43)id 1DZdyn-0004ao-BWfor [EMAIL PROTECTED]; Sat, 21 May
2005 20:06:05 -0400
X-Message-Info: JGTYoYF78jFrDPPrXactE4Nmd+8aFpukTHQNjIsPyMM=
Path:
shelby.stanford.edu!newsfeed.stanford.edu!bloom-beacon.mit.edu!panix!not-for-mail
Newsgroups: gnu.cvs.help
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 25
References: <[EMAIL PROTECTED]>
NNTP-Posting-Host: panix1.panix.com
X-Trace: reader1.panix.com 1116720028 5720 166.84.1.1 (22 May 2005
00:00:28GMT)
X-Complaints-To: [EMAIL PROTECTED]
NNTP-Posting-Date: Sun, 22 May 2005 00:00:28 +0000 (UTC)
User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (NetBSD/2.0 (i386))
Xref: shelby.stanford.edu gnu.cvs.help:45095
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Announcements and discussions for the CVS version control
system<info-cvs.gnu.org>
List-Unsubscribe:
<http://lists.gnu.org/mailman/listinfo/info-cvs>,<mailto:[EMAIL PROTECTED]>
List-Archive: <http://lists.gnu.org/pipermail/info-cvs>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe:
<http://lists.gnu.org/mailman/listinfo/info-cvs>,<mailto:[EMAIL PROTECTED]>
Errors-To: [EMAIL PROTECTED]
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 22 May 2005 00:04:11.0940 (UTC)
FILETIME=[C88C3E40:01C55E61]
Christian Hujer <[EMAIL PROTECTED]> wrote:
> What is the best way to make the HEAD revision of the files being the
previous
> revision? I've read the faq, they say if the last version is 1.31,
"checkout
> 1.30 and recheckin as 1.32". But I cannot imagine how to do this.
cvs update -j 1.31 -j 1.30 the_file
or
cvs update -p -r1.30 the_file > the_file
> When I try "cvs update -r 1.30 file" and then "cvs commit file" it of
course
> does not work.
Because it has a sticky revision. To recover from that,
cp the_file tempfile
cvs update -A the_file
mv tempfile the_file
Any one of these three methods will give you a file with the content of
revision 1.30, ready to be committed as revision 1.32 .
--
pa at panix dot com
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs
