Ouch,
I have messed up the TLA tree many times by trying to commit only the emulator changes. I guess patch-36 to patch-38 are mistakes. I hope I didn't mess the tree too much.
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
On Thu, 2005-06-09 at 15:04 -0600, Li-Ta Lo wrote:
Ouch,
I have messed up the TLA tree many times by trying to commit only the emulator changes. I guess patch-36 to patch-38 are mistakes. I hope I didn't mess the tree too much.
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
What is the equivalent of "cvs diff -rX.Y -rX.Z"?
On Thu, Jun 09, 2005 at 03:20:57PM -0600, Li-Ta Lo wrote:
On Thu, 2005-06-09 at 15:04 -0600, Li-Ta Lo wrote:
I have messed up the TLA tree many times by trying to commit only the emulator changes. I guess patch-36 to patch-38 are mistakes. I hope I didn't mess the tree too much.
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
What is the equivalent of "cvs diff -rX.Y -rX.Z"?
Have you seen:
http://wiki.gnuarch.org/Learning_20Arch_20commands_20for_20CVS_20users
?
It suggests:
cvs diff -r 1.2 -r 1.5 == tla delta --diffs patch-2 patch-5
For the backing out a changeset I found:
http://wiki.gnuarch.org/Arch_20Recipes#head-13d35cf3d0899c602e4e054cd7e962e6...
J.
On Thu, Jun 09, 2005 at 03:20:57PM -0600, Li-Ta Lo wrote:
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
For the backing out a changeset I found:
http://wiki.gnuarch.org/Arch_20Recipes#head-13d35cf3d0899c602e4e054cd7e962e6...
Does this roll back "tla add", "tla rm" and "tla mv" ? What do these commands do to the repository? Are they just local until a "tla commit" like their cvs counterparts?
One reason we tried to switch to some VCS with "automatic" operation is to be easy to roll back these commands.
Ollie
On Thu, Jun 09, 2005 at 06:30:07PM -0600, Li-Ta Lo wrote:
On Thu, Jun 09, 2005 at 03:20:57PM -0600, Li-Ta Lo wrote:
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
For the backing out a changeset I found:
http://wiki.gnuarch.org/Arch_20Recipes#head-13d35cf3d0899c602e4e054cd7e962e6...
Does this roll back "tla add", "tla rm" and "tla mv" ? What do these commands do to the repository? Are they just local until a "tla commit" like their cvs counterparts?
Yes, add, rm & mv all just affect your local tree checkout until you commit them.
Try looking at the rest of the http://wiki.gnuarch.org/Arch_20Recipes page. "Fixing your own mistakes" seems to be the section you want.
One reason we tried to switch to some VCS with "automatic" operation is to be easy to roll back these commands.
I've not had to do it myself (yet), but it looks like arch can handle this without a problem.
J.
On Thu, 2005-06-09 at 15:04 -0600, Li-Ta Lo wrote:
Ouch,
I have messed up the TLA tree many times by trying to commit only the emulator changes. I guess patch-36 to patch-38 are mistakes. I hope I didn't mess the tree too much.
BTW, how exactly should I roll back a patch level ? Is the "tla replay --revers" plus "tla sync-tree" the right way to do? Does it undo "tla add"?
Holy shit, why can't I see any file on the TLA web interface for patch-36 and later?
-
Jonathan McDowell -
Li-Ta Lo