From: fork0@t-online.de (Alex Riesen)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Nasty git corruption problem
Date: Wed, 26 Jul 2006 23:55:36 +0200 [thread overview]
Message-ID: <20060726215536.GA6046@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0607260945440.29649@g5.osdl.org>
Linus Torvalds, Wed, Jul 26, 2006 19:07:07 +0200:
> In fact, if you want to play around with a git patch, this trivial one
> should make git-fsck-objects create those lost-and-found entries
> automatically if you give it the "--lost-n-found" flag.
there is git-lost-found already. Still, it somewhat expected of fsck
to do such things.
prev parent reply other threads:[~2006-07-26 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 16:01 Alan Cox
2006-07-26 17:07 ` Linus Torvalds
2006-07-26 17:36 ` Johannes Schindelin
2006-07-26 17:41 ` Linus Torvalds
2006-07-26 17:43 ` Linus Torvalds
2006-07-27 18:32 ` Alan Cox
2006-07-27 19:07 ` Linus Torvalds
2006-07-27 20:48 ` Johannes Schindelin
2006-07-27 21:01 ` Linus Torvalds
2006-07-27 21:11 ` Johannes Schindelin
2006-07-26 18:09 ` Carl Worth
2006-07-26 21:55 ` Alex Riesen [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=20060726215536.GA6046@steel.home \
--to=fork0@t-online.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®