[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-gnu-arch] [bug #5112] Rework replay command-line processing
From: |
nobody |
Subject: |
[Bug-gnu-arch] [bug #5112] Rework replay command-line processing |
Date: |
Sat, 06 Sep 2003 22:16:33 -0400 |
User-agent: |
Mozilla/4.76 [en] (X11; U; FreeBSD 3.0-RELEASE i386) |
=================== BUG #5112: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5112&group_id=4899
Changes by: Tom Lord <address@hidden>
Date: Sat 09/06/2003 at 19:16 (US/Pacific)
------------------ Additional Follow-up Comments ----------------------------
Formerly,
tla replay REVISION
would replay all revisions from the one just past the
most recent revision my tree already has, up to REVISION.
How do I do this after these changes?
The `update' command invokes the `replay' command.
Does that still work correctly?
-t
=================== BUG #5112: FULL BUG SNAPSHOT ===================
Submitted by: miles Project: GNU arch -- a revision control
system
Submitted on: Sat 09/06/2003 at 19:02
Category: tla Severity: 5 - Major
Bug Group: small feature idea Resolution: None
Status: Open Release:
address@hidden/tla--devo--1.1--patch-153
Fixed Release: address@hidden/tla--devo--1.1--patch-29Merge Request?: yes --
merge from my archive
Your Archive Name: address@hidden Archive Location:
http://arch.linuxguru.net/~miles/address@hidden
Assigned to: None
Summary: Rework replay command-line processing
Original Submission: (1) Remove the --exact option. Now if you specify a
revision, it will apply (or reverse) exactly that revision, and if you specify
a version it will apply missing/new patches in that version.
I think this new usage is far more natural; --exact always seemed
superfluous (`I specified a revision, why can't it know to just apply that
revision?!?'), sort of like --files did.
(2) Allow multiple version/revision arguments. I've often wanted to replay
multiple changesets at once, and it's a minor convenience to be able to give
them all on the command line. It's probably less useful for version arguments,
but I implemented that too for consistency's sake.
(3) Do more rigorous argument checking, and hopefully improve the error
messages a bit.
(4) Eliminate all the duplicate code between the `missing' and `new' cases.
Follow-up Comments
*******************
-------------------------------------------------------
Date: Sat 09/06/2003 at 19:16 By: tomlord
Formerly,
tla replay REVISION
would replay all revisions from the one just past the
most recent revision my tree already has, up to REVISION.
How do I do this after these changes?
The `update' command invokes the `replay' command.
Does that still work correctly?
-t
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5112&group_id=4899
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/