From: Alex Riesen <raa.lkml@gmail.com>
To: Pierre Habouzit <madcoder@debian.org>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH 04/25] Rework make_usage to print the usage message immediately
Date: Tue, 16 Oct 2007 19:56:50 +0200 [thread overview]
Message-ID: <20071016175650.GA9992@steel.home> (raw)
In-Reply-To: <1192523998-19474-4-git-send-email-madcoder@debian.org>
Pierre Habouzit, Tue, Oct 16, 2007 10:39:37 +0200:
> From: Alex Riesen <raa.lkml@gmail.com>
>
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> ---
> parse-options.c | 48 ++++++++++++++++++++++--------------------------
> 1 files changed, 22 insertions(+), 26 deletions(-)
Got it three times: you put git@kernel.org into To: and Cc:
Why stderr, BTW? For instance, the output from "git help" is on
stdout. To be fair, I don't know why it is stdout there either.
next prev parent reply other threads:[~2007-10-16 17:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 8:16 [parse-options] proposal for merge, take 1 Pierre Habouzit
2007-10-16 8:20 ` Pierre Habouzit
2007-10-16 8:43 ` Pierre Habouzit
[not found] ` <1192523998-19474-1-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-2-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-3-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-4-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-5-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-6-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-7-git-send-email-madcoder@debian.org>
2007-10-16 8:45 ` [PATCH 07/25] parse-options: make some arguments optional, add callbacks Pierre Habouzit
2007-10-16 13:18 ` Johannes Schindelin
2007-10-16 16:38 ` René Scharfe
2007-10-16 16:44 ` Johannes Schindelin
2007-10-16 16:53 ` Pierre Habouzit
2007-10-16 17:21 ` Nicolas Pitre
2007-10-16 17:04 ` René Scharfe
2007-10-16 16:44 ` Nicolas Pitre
2007-10-16 16:50 ` Pierre Habouzit
2007-10-17 4:44 ` Shawn O. Pearce
2007-10-17 18:00 ` Johannes Schindelin
[not found] ` <1192523998-19474-8-git-send-email-madcoder@debian.org>
[not found] ` <1192523998-19474-9-git-send-email-madcoder@debian.org>
2007-10-16 8:55 ` [PATCH 09/25] Port builtin-add.c to use the new option parser Michael Witten
2007-10-16 9:36 ` Michael Witten
2007-10-16 13:17 ` Johannes Schindelin
2007-10-16 15:36 ` Michael Witten
2007-10-16 16:55 ` Pierre Habouzit
2007-10-16 17:56 ` Alex Riesen [this message]
2007-10-16 22:15 ` [PATCH 04/25] Rework make_usage to print the usage message immediately Pierre Habouzit
2007-10-17 19:06 ` Alex Riesen
[not found] ` <1192523721-18985-1-git-send-email-madcoder@debian.org>
2007-10-17 7:24 ` [PATCH 01/25] Add a simple option parser Shawn O. Pearce
2007-10-17 7:52 ` Pierre Habouzit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071016175650.GA9992@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).