From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] fsck --lost-found writes to subdirectories in .git/lost-found/
Date: Wed, 4 Jul 2007 02:41:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707040240320.4071@racer.site> (raw)
In-Reply-To: <20070704013311.GA32210@diku.dk>
Hi,
On Wed, 4 Jul 2007, Jonas Fonseca wrote:
> - Write dangling refs into .git/commit/ or .git/other/, depending
> - on type.
> + Write dangling refs into .git/lost-found/commit/ or
> + .git/lost-found/other/, depending on type.
Oooooops.
Thanks,
Dscho
prev parent reply other threads:[~2007-07-04 1:41 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
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 [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=Pine.LNX.4.64.0707040240320.4071@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=fonseca@diku.dk \
--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).