Aloa, Henrik Theiling wrote: > I disagree: all status messages should go to stderr, because stdout should > be reserved for carrying application output. This way, you can use > programs in a unix pipe to pass application output to the next application > while still a) being able to read all messages, b) avoiding contamination > of the stdout stream with messages. but this is not the case currently, afaics at all other places in the source, if there is a status message about success (e.g. opening/deleting key slots), it goes to stdout, otherwise it goes to stderr. > There should be a clear distinction between application data (stdout) > and user messages (stderr). This sounds reasonable, I hope that more will post their opinion about this, because this would be a bigger change. Regards, Till --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
