[cvsnt-dev] Commit -k ?

Oliver Giesen ogware at gmx.net
Wed Dec 1 17:31:53 GMT 2004

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

news:mailman.2792.1101921465.21094.cvsnt-commits at cvsnt.org...
> CVSROOT: /usr/local/cvs
> Module name: cvsnt
> Repository: cvsnt/src/
> Changes by: tmh at sisko.local.nodomain.org. 04/12/01 17:17:06
> Modified files:
> cvsnt/src/: Tag: CVSNT_2_0_x commit.cpp cvs.h edit.cpp
> Log message:
> Commit -k to keep edit

Does this make sense? IMO -k belongs to the "common" options (i.e. which
have a common meaning across commands, like -r or -l). For consistency, I
don't think it should be "reimplemented" with a completely different meaning
here even if committing with a specified keyword expansion mode is currently
not available. How about commit -e or something like that? Anyway, how hard
is it to just press Edit again after the commit? Why overcomplicate things
by cluttering the CLI? Keep the interface simple and let the GUI clients
take care of combined operations.


----  ------------------
JID:  ogiesen at jabber.org
ICQ:  18777742     (http://wwp.icq.com/18777742)

More information about the cvsnt-dev mailing list