From: Pierre Habouzit <madcoder@debian.org>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: spearce@spearce.org, gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Fixed a command line option type for builtin-fsck.c
Date: Tue, 30 Oct 2007 21:20:50 +0100 [thread overview]
Message-ID: <20071030202050.GA9776@artemis.corp> (raw)
In-Reply-To: <1193771721-2880-1-git-send-email-Emilian.Medve@Freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Tue, Oct 30, 2007 at 07:15:21PM +0000, Emil Medve wrote:
> The typo was introduced by this commit: 5ac0a2063e8f824f6e8ffb4d18de74c55aae7131
>
> Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
Acked-By: Pierre Habouzit <madcoder@debian.org>
good catch.
> ---
>
> This patch applies to the 'next' branch
>
> builtin-fsck.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/builtin-fsck.c b/builtin-fsck.c
> index 64da3bd..e4874f6 100644
> --- a/builtin-fsck.c
> +++ b/builtin-fsck.c
> @@ -680,7 +680,7 @@ static struct option fsck_opts[] = {
> OPT_BOOLEAN(0, "cache", &keep_cache_objects, "make index objects head nodes"),
> OPT_BOOLEAN(0, "reflogs", &include_reflogs, "make reflogs head nodes (default)"),
> OPT_BOOLEAN(0, "full", &check_full, "also consider alternate objects"),
> - OPT_BOOLEAN(0, "struct", &check_strict, "enable more strict checking"),
> + OPT_BOOLEAN(0, "strict", &check_strict, "enable more strict checking"),
> OPT_BOOLEAN(0, "lost-found", &write_lost_and_found,
> "write dangling objects in .git/lost-found"),
> OPT_END(),
> --
> 1.5.3.4.1458.g3e72e-dirty
>
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-10-30 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 19:15 [PATCH] Fixed a command line option type for builtin-fsck.c Emil Medve
2007-10-30 20:20 ` Pierre Habouzit [this message]
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=20071030202050.GA9776@artemis.corp \
--to=madcoder@debian.org \
--cc=Emilian.Medve@Freescale.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).