Re: too much for an NMU?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> David H. Silber wrote:
> > On Fri, Jul 23, 1999 at 07:09:07PM -0700, Darren/Torin/Who Ever... wrote:
> > > I'd like to fix the following bugs but I'm worried that I might be
> > > stepping pasts the bounds of an NMU to fix them:
> > > #34423: pilot-xfer: "press hotsync" should be on stderr
> > I don't think that this is a real bug. This is somebody's preference.
> > (Unless a whole lot of people agree.)
> Seems a weird thing to ask for, to moi. Def not a bug.
> bekj
Short Form: I think it should be on stderr because pressing the hotsync
button requires user intervention and is not part of the normal progress
of the program (it's not necessary if you've already done it, and may not
be necessary with future Palm models with AutoSync[TM] cradles or 3Com
knows what).
Long Form: Depending on your philosophy, stderr is usually reserved for
exceptional circumstances that require user intervention. Pressing
Hotsync would appear, to me, to be an exceptional circumstance, and thus
be put on stderr. As a rule of thumb, I think of it in a GUI environment.
If it's in a popup dialog, it should come from stderr. If it's pipe
output or, in the case of the transfer progress like the status indicators
in pilot-link, a normal indicator of program progress, it should come from
stdout. So, Press Hotsync should come from stderr but the status messages
should continue to come from stdout due to the nature of their importance.
In general, pilot-xfer is not an interactive program. Stdout should be
used to record its progress. Stderr should note exceptional circumstances
that require user intervention or note such as errors in the byte stream
and pressing the hotsync button. That's just my opinion, I could be
wrong.
Jayson Vantuyl
Code Jockey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.8 (GNU/Linux)
Comment: Made with PGP4Pine
iD8DBQE3mxzSlBv9MedxyboRAoXEAKCCWFsv+g6qTpKx5Jt9bSbb4VGgPQCgxSBZ
muZNi7Y6rDxJrBTxh6hlbdQ=
=qw10
-----END PGP SIGNATURE-----
Reply to: