From: Jesse van den Kieboom <jesse@icecrew.nl>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder@fzi.de>
Subject: Re: [PATCH 1/3] Fix "multi-character character constant" compile warning
Date: Wed, 04 Feb 2009 12:50:56 +0100 [thread overview]
Message-ID: <1233748256.7594.3.camel@wren> (raw)
In-Reply-To: <1233666531-21589-1-git-send-email-szeder@ira.uka.de>
Op dinsdag 03-02-2009 om 14:08 uur [tijdzone +0100], schreef SZEDER
Gábor:
> From: SZEDER Gábor <szeder@fzi.de>
>
> ... that was caused by a short command line option.
>
> Signed-off-by: SZEDER Gábor <szeder@ira.uka.de>
> ---
> gitg/gitg.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/gitg/gitg.c b/gitg/gitg.c
> index 1b33294..69c5b56 100644
> --- a/gitg/gitg.c
> +++ b/gitg/gitg.c
> @@ -15,7 +15,7 @@ static gboolean commit_mode = FALSE;
>
> static GOptionEntry entries[] =
> {
> - { "commit", '-c', 0, G_OPTION_ARG_NONE, &commit_mode, N_("Start gitg in commit mode") },
> + { "commit", 'c', 0, G_OPTION_ARG_NONE, &commit_mode, N_("Start gitg in commit mode") },
> { NULL }
> };
This has already been fixed.
--
Jesse van den Kieboom
Personal: http://www.icecrew.nl
Professional: http://www.novowork.com
next prev parent reply other threads:[~2009-02-04 11:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 20:05 git gtk+/GNOME gui application: gitg Jesse van den Kieboom
2009-02-03 13:08 ` SZEDER Gábor
2009-02-03 13:08 ` [PATCH 1/3] Fix "multi-character character constant" compile warning SZEDER Gábor
2009-02-03 13:08 ` [PATCH 2/3] Refactor loading xml UI files SZEDER Gábor
2009-02-03 13:08 ` [PATCH 3/3] Try load UI xml files from the current working directory SZEDER Gábor
2009-02-14 21:37 ` [PATCH 2/3] Refactor loading xml UI files Jesse van den Kieboom
2009-02-04 11:50 ` Jesse van den Kieboom [this message]
2009-02-03 16:58 ` git gtk+/GNOME gui application: gitg Michael J Gruber
2009-02-03 19:43 ` Stefan Karpinski
2009-02-04 11:50 ` Jesse van den Kieboom
2009-02-04 3:38 ` Miles Bader
2009-02-03 17:00 ` Jakub Narebski
[not found] ` <1233748909.7594.14.camel@wren>
2009-02-04 12:33 ` Jakub Narebski
2009-02-04 7:39 ` Felipe Contreras
2009-02-04 11:48 ` Jesse van den Kieboom
2009-02-04 12:46 ` Michael J Gruber
2009-02-04 14:12 ` Felipe Contreras
2009-02-04 14:18 ` Jesse van den Kieboom
2009-02-04 15:00 ` Felipe Contreras
2009-02-04 14:29 ` Michael J Gruber
2009-02-04 14:33 ` Jesse van den Kieboom
2009-02-04 14:40 ` Michael J Gruber
2009-02-04 14:46 ` Jesse van den Kieboom
2009-02-05 5:46 ` Miles Bader
2009-02-05 20:06 ` Jesse van den Kieboom
2009-02-06 9:49 ` Miles Bader
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233748256.7594.3.camel@wren \
--to=jesse@icecrew.nl \
--cc=git@vger.kernel.org \
--cc=szeder@fzi.de \
--cc=szeder@ira.uka.de \
/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.
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 NNTP newsgroup(s).