From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-fsck: add --lost-found option
Date: Mon, 02 Jul 2007 17:08:25 -0700 [thread overview]
Message-ID: <7vps3auz5y.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707030018120.4071@racer.site> (Johannes Schindelin's message of "Tue, 3 Jul 2007 00:26:37 +0100 (BST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> WARNING: 'git lost-found' is deprecated.
> WARNING: Use 'git fsck --lost-found' instead
>
> whenever lost-found is called?
I agree that would be a sensible second step after the result of
the first step matures.
>> 3. git-lost-found is removed.
>
> Yes, that can wait.
>
> What is more important before doing 1&2 for real is this: lost-found ATM
> calls 'git-fsck --full --no-reflogs'. The patch does not force these two
> options when called with '--lost-found'. I would really appreciate
> opinions on this issue, and will gladly re-prepare a patch accordingly.
I think I am not following you; do you mean --lost-found does
not imply these two? I am not sure if there is any benefit of
being able to do --lost-found without --full nor --no-reflogs.
next prev parent reply other threads:[~2007-07-03 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 16:53 [PATCH] git-fsck: add --lost-found option Johannes Schindelin
2007-07-02 23:11 ` Junio C Hamano
2007-07-02 23:26 ` Johannes Schindelin
2007-07-03 0:08 ` Junio C Hamano [this message]
2007-07-03 0:33 ` Johannes Schindelin
2007-07-04 1:33 ` [PATCH] fsck --lost-found writes to subdirectories in .git/lost-found/ Jonas Fonseca
2007-07-04 1:41 ` Johannes Schindelin
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=7vps3auz5y.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.