| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1225.1 | Re: submitting an previous rev of a checked out file | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jan 26 1995 20:46 | 40 |
| Date Of Receipt: 26-JAN-1995 16:36:45.50
From: SMURF::ALPHA::"vandyck@cardinal.zk3.dec.com" "26-Jan-1995 1635"
To: "Rich Larsen rll@unx.dec.com" <rll@unx.dec.com>
CC: odehelp@zk3.dec.com
Subj: Re: submitting an previous rev of a checked out file
Just outdate the 1.2.2.2 and 1.2.2.3 versions using bcs -o.
If you look at the manpage for bcs you can see how to outdate a range.
-o[range]
Outdates revisions given by range; if no range is given, removes
branch and all revisions contained in private branch. For example;
the command bcs -o4-6 outdates versions 4,5, and 6 on the current
branch.
-Grant
|
| Is there a clean way to submit an earlier version of a file
| that is checked out onto a branch. For example, I created a
| new file and do a number of bco/bci's on the branch of that
| file. The latest rev of that file is say, 1.2.2.3 and I want
| to submit version 1.2.2.1. Can I submit version 1.2.2.1 from
| that same branch in that sandbox?
|
| Rich
| ================================================================
| Rich Larsen, M/S: UNX TCP/IP: rll@unx.dec.com
| USSG/User Env. & Std. Group DECnet: UNXA::LARSEN
| Digital Equipment Corporation FAX: 908-577-6003
| 200 Route 9 North Voice: 908-577-6083
| Manalapan, New Jersey 07726 DTN: 462
-Grant
|
| 1225.2 | Re: submitting an previous rev of a checked out file | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jan 26 1995 20:47 | 10 |
| Date Of Receipt: 26-JAN-1995 17:01:08.28
From: SMURF::FLAMBE::"rll@unx.dec.com" "26-Jan-1995 1656"
To: "Grant Van Dyck" <vandyck@cardinal.zk3.dec.com>
CC: "Rich Larsen rll@unx.dec.com" <rll@unx.dec.com>, odehelp@zk3.dec.com
Subj: Re: submitting an previous rev of a checked out file
That sounds fine but what if I want to save 1.2.2.2 and 1.2.2.3.
-Rich
|
| 1225.3 | Re: submitting an previous rev of a checked out file | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Jan 27 1995 01:57 | 24 |
| Date Of Receipt: 26-JAN-1995 22:27:47.86
From: SMURF::QUARRY::"vandyck@cardinal.zk3.dec.com"
To: rll@unx.dec.com (Rich Larsen rll@unx.dec.com)
CC: vandyck@cardinal.zk3.dec.com, rll@unx.dec.com, odehelp@zk3.dec.com
Subj: Re: submitting an previous rev of a checked out file
> That sounds fine but what if I want to save 1.2.2.2 and 1.2.2.3.
>
Ah well that's a horse of a different color.
bco -r1.2.2.1 -u foo.c
mv foo.c foo.save
bco foo.c
mv foo.save foo.c
bci foo.c
bsubmit -noauto_out foo.c #You must do this else your private branch goes
away.
--
Grant Van Dyck enet: vandyck@zk3.dec.com
Release Engineering
|
| 1225.4 | Re: submitting an previous rev of a checked out file | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Jan 27 1995 06:00 | 37 |
| Date Of Receipt: 27-JAN-1995 02:03:47.71
From: SMURF::FLUME::jmcg "Jim McGinness"
To: vandyck@zk3.dec.com
CC: odehelp@DEC:.zko.flume, rll@unx.dec.com
Subj: Re: submitting an previous rev of a checked out file
That submits 1.2.2.4, which is a copy of 1.2.2.1, rather than submitting
1.2.2.1.
To clean up (return to the _status_quo_ante_), he has to then outdate the
1.2.2.4 revision.
bcs -o1.2.2.4 foo.c
I spent some time trying to figure out a cleaner way and found I was in the
same quandry as with the "revert" problem. While there are RCS commands that
might do what's needed, there's just no way to get there through ODE. The
closest I came to something "clean" was do Grant's suggestion in a new
sandbox.
bci foo.c # else it can't be checked out in the new sb
mksb -back ... newsb
workon -sb newsb
bco -r1.2.2.1 -u foo.c
mv foo.c foo.save
bco foo.c
cp foo.save foo.c
bci -m"Same as Rev1.2.2.1" foo.c
bsubmit foo.c
exit
mksb -undo newsb
Too many steps.
-- jmcg
|