From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: repack: handling of .keep files
Date: Fri, 4 May 2007 19:24:50 +0200 [thread overview]
Message-ID: <81b0412b0705041024i43d7fc5ah1967d6a6192dc6ee@mail.gmail.com> (raw)
In-Reply-To: <7vslacttij.fsf@assigned-by-dhcp.cox.net>
On 5/4/07, Junio C Hamano <junkio@cox.net> wrote:
> "Alex Riesen" <raa.lkml@gmail.com> writes:
>
> > Still, git-log shouldn't crash (nothing should, of course).
>
> Honestly, I think that's borderline. If you "dd if=/dev/random
> of=/dev/hda", should the kernel keep going, perhaps gracefully
> declining access to the filesystem on that drive?
e2fsck has a test somewhere which randomly corrupts a partition
and then lets the program fix it.
All kind of corruptions happen, we will have to deal with them.
Especially if this crash is so simple to reproduce.
> case of temporary pack I do not think there would be a risk of
> filename collisions, I think it makes sense to use either
> GIT_DIR or GIT_OBJECT_DIRECTORY instead of the working tree.
>
> I do not know pros-and-cons between .git/ and .git/objects/;
These are settable separately, so theoretically you can end
up with .git and .git/objects being on different filesystems.
Atomic rename wont be possible than.
next prev parent reply other threads:[~2007-05-04 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 9:25 repack: handling of .keep files Alex Riesen
2007-05-04 9:56 ` Junio C Hamano
2007-05-04 10:42 ` Alex Riesen
2007-05-04 16:59 ` Junio C Hamano
2007-05-04 17:24 ` Alex Riesen [this message]
2007-05-04 19:20 ` Junio C Hamano
[not found] ` <20070507173324.GA3436@steel.home>
2007-05-07 17:51 ` [PATCH] Use GIT_OBJECT_DIR for temporary files of pack-objects Dana How
2007-05-07 21:33 ` Alex Riesen
2007-05-07 21:59 ` Dana How
2007-05-04 19:40 ` repack: handling of .keep files Nicolas Pitre
2007-05-04 21:54 ` [PATCH] Handle return code of parse_commit in revision machinery Alex Riesen
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=81b0412b0705041024i43d7fc5ah1967d6a6192dc6ee@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).