From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-fsck: add --lost-found option
Date: Tue, 3 Jul 2007 00:26:37 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707030018120.4071@racer.site> (raw)
In-Reply-To: <7vabuewgdb.fsf@assigned-by-dhcp.cox.net>
Hi,
On Mon, 2 Jul 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > With this option, dangling objects are not only reported, but also
> > written to .git/lost-found/commit/ or .git/lost-found/other/.
> >
> > This obsoletes git-lost-found.
>
> [...]
>
> Please do not do that in a single patch. This patch is at least
> talking about three timeframes.
Right. My fault.
> 1. git-fsck learns --lost-found
> The patch adds that to the code and the documentation.
> Then it is commented on, perhaps updated, and matures.
>
> 2. git-lost-found is marked as "deprecated"
> This patch adds "deprecated" warning to the documentation.
How about combining these two, and give a big
WARNING: 'git lost-found' is deprecated.
WARNING: Use 'git fsck --lost-found' instead
whenever lost-found is called?
> 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.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-02 23:26 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 [this message]
2007-07-03 0:08 ` Junio C Hamano
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=Pine.LNX.4.64.0707030018120.4071@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).