| TODO (54427) | TODO (66525) |
|---|---|
| 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 --- 501 unchanged lines hidden (view full) --- 510one is the most tolerant of flaky networks; if checkins happen at each 511site independently there is no particular problem. The big question 512is whether merges happen only manually, as with existing CVS branches, 513or whether there is a feature whereby there are circumstances in which 514merges from one branch to the other happen automatically (for example, 515the case in which the branches have not diverged). This might be a 516legitimate question to ask even quite aside from multisite features. 517 | 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 --- 501 unchanged lines hidden (view full) --- 510one is the most tolerant of flaky networks; if checkins happen at each 511site independently there is no particular problem. The big question 512is whether merges happen only manually, as with existing CVS branches, 513or whether there is a feature whereby there are circumstances in which 514merges from one branch to the other happen automatically (for example, 515the case in which the branches have not diverged). This might be a 516legitimate question to ask even quite aside from multisite features. 517 |
| 518One additional random tidbit is to note that Eric Raymond has some 519interest in this sort of thing. The item "Cooperative distributed 520freeware development" on http://www.ccil.org/~esr/ has a very brief 521introduction to what he is thinking about. 522 | |
| 523187. Might want to separate out usage error messages and help 524messages. The problem now is that if you specify an invalid option, 525for example, the error message is lost among all the help text. In 526the new regime, the error message would be followed by a one-line 527message directing people to the appropriate help option ("cvs -H 528<command>" or "cvs --help-commands" or whatever, according to the 529situation). I'm not sure whether this change would be controversial 530(as defined in HACKING), so there might be a need for further --- 267 unchanged lines hidden --- | 518187. Might want to separate out usage error messages and help 519messages. The problem now is that if you specify an invalid option, 520for example, the error message is lost among all the help text. In 521the new regime, the error message would be followed by a one-line 522message directing people to the appropriate help option ("cvs -H 523<command>" or "cvs --help-commands" or whatever, according to the 524situation). I'm not sure whether this change would be controversial 525(as defined in HACKING), so there might be a need for further --- 267 unchanged lines hidden --- |