| TODO (32785) | TODO (34461) |
|---|---|
| 1The "TODO" file! -*-Indented-Text-*- 2 322. Catch signals for cleanup when "add"ing files. 4 524. Insist on a log message. 6 (If done, this should be configurable via commitinfo or some new 7 config file -kingdon, Jun 1995). 8 --- 628 unchanged lines hidden (view full) --- 637 638 c. Suppressing various error messages. This is almost surely 639 bogus. 640 641 commit.c: failed to remove tag `%s' from `%s' (Questionable. 642 Rationale might be that we already printed another message 643 elsewhere but why would it be necessary to avoid 644 the extra message in such an uncommon case?) | 1The "TODO" file! -*-Indented-Text-*- 2 322. Catch signals for cleanup when "add"ing files. 4 524. Insist on a log message. 6 (If done, this should be configurable via commitinfo or some new 7 config file -kingdon, Jun 1995). 8 --- 628 unchanged lines hidden (view full) --- 637 638 c. Suppressing various error messages. This is almost surely 639 bogus. 640 641 commit.c: failed to remove tag `%s' from `%s' (Questionable. 642 Rationale might be that we already printed another message 643 elsewhere but why would it be necessary to avoid 644 the extra message in such an uncommon case?) |
| 645 commit.c: failed to check out `%s' (likewise; this one seems to be a 646 vestige from before RCS_checkout was internal. Take a look at how 647 RCS_checkout handles errors) | |
| 648 commit.c: failed to commit dead revision for `%s' (likewise) 649 remove.c: file `%s' still in working directory (see below about rm 650 -f analogy) 651 remove.c: nothing known about `%s' (looks dubious to me, especially in 652 the case where the user specified it explicitly). 653 remove.c: removed `%s' (seems like an obscure enough case that I fail 654 to see the appeal of being cryptically concise here). 655 remove.c: file `%s' already scheduled for removal (now it is starting --- 138 unchanged lines hidden --- | 645 commit.c: failed to commit dead revision for `%s' (likewise) 646 remove.c: file `%s' still in working directory (see below about rm 647 -f analogy) 648 remove.c: nothing known about `%s' (looks dubious to me, especially in 649 the case where the user specified it explicitly). 650 remove.c: removed `%s' (seems like an obscure enough case that I fail 651 to see the appeal of being cryptically concise here). 652 remove.c: file `%s' already scheduled for removal (now it is starting --- 138 unchanged lines hidden --- |