[notmuch] "notmuch help" outputs to stderr?
cworth at cworth.org
Wed Nov 18 08:29:20 PST 2009
On Tue, 17 Nov 2009 20:01:16 -0500, Lars Kellogg-Stedman <lars at seas.harvard.edu> wrote:
> > I've attached a patch that lets usage() take a FILE * argument so that
> > you can output to stderr in response to usage errors, and stdout in
> > response to an explicit request.
> Whoops, missed a couple of stderr's in that last patch. New one
> Lars Kellogg-Stedman <lars at seas.harvard.edu>
> Senior Technologist, Computing and Information Technology
> Harvard University School of Engineering and Applied Sciences
That was obviously a bug, so I really appreciate both your report and
BTW, for future patches, it would be easier for me, (and hopefully not
too much harder for you), if you could format your mails so that "git
am" will find a good commit message in them. There are a few different
ways you can do that:
Option (1) takes more work upfront to get comfortable with it and to
make sure it works, but it's probably less work (particuarly 1.b with
"git send-email) once you get into the flow of it. Option (2) is
probably the least different from what you're currently doing.
1. Make a commit locally with the commit message. Then run "git
format-patch", (with "git format-patch HEAD~N" where N is the number
of commits you want to generate), to generate formatted email
messages, (or even an entire mbox).
a. Suck those messages up into an email program. Add any commentary
(to not be part of the commit message) after the --- separator and
b. Use "git send-email" to fire the messages off.
2. Just attach the "git diff" output like you did, but then carefully
word the subject and body of the email message to look like a commit
message. You can again use a --- separator for commentary that's not
part of the patch.
For example, option (2) would have looked like the below to generate the
commit message I ended up using for your commit.
Anyway, thanks again,
Subject: [Patch] notmuch help: Print to stdout, not to stderr.
Let usage() take a FILE * argument so that you can output to stderr in
response to usage errors, and stdout in response to an explicit request.
Whoops, missed a couple of stderr's in that last patch. New one
Lars Kellogg-Stedman <lars at seas.harvard.edu>
Senior Technologist, Computing and Information Technology
Harvard University School of Engineering and Applied Sciences
More information about the notmuch