[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help! Disappearing log messages
From: |
address@hidden |
Subject: |
Re: Help! Disappearing log messages |
Date: |
Thu, 27 May 2004 15:02:41 -0400 |
J Krugman writes:
>
> This was the problem! Thanks!! (I can't believe commit fails
> silently like this.)
It doesn't fail, it works just fine. Commit commits *changes*; if there
aren't any changes, then there's nothing to commit!
> During
> my *very* short acquaintance with CVS, I've already come across
> many oddities. Its exit status is meaningless, apparently.
That's because a typical command performs a bunch of functions and it's
quite possible for some of them to succeed and some of them to fail. It's
not at all clear how to encode that into a single exit status.
> The global -Q flag works for some commands, but not for others.
That's a valid criticism. My impression is that -q and -Q have evolved as
various developers have decided that particular messages are more or less
useful. I also get the impression that developers have added messages
without any consideration as to which option should suppress them, if any.
> CVS does not save any human-readable information about tags.
What information would you have it save? People use tags for a very wide
variety of reasons; in most cases, the name of the tag is the only property
of interest. CVS does provide facilities for recording additional data if
you want to do so.
> None of this is super-awful; just a lot of small-time weirdness.
It's only weird because it doesn't match your expectations; if you come to
CVS without a bunch of preconceived notions about how it ought to work, it
makes a lot more sense. :-)
-Larry Jones
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
- Re: Help! Disappearing log messages,
address@hidden <=