From: Junio C Hamano <gitster@pobox.com>
To: "Jason Sewall" <jasonsewall@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: New repo quickly corrupted
Date: Thu, 15 Nov 2007 13:55:40 -0800 [thread overview]
Message-ID: <7vejer41ib.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <31e9dd080711151350u6c2ae40foc7c05e59496260fa@mail.gmail.com> (Jason Sewall's message of "Thu, 15 Nov 2007 16:50:15 -0500")
"Jason Sewall" <jasonsewall@gmail.com> writes:
> find . -type f -exec dos2unix {} +
> git commit -a --amend
> [accept same message]
> git fsck
> [same error message as above]
>
> I just built my git today, unmodified:
> git version 1.5.3.5.721.g039b
>
> What's going on?
Carelessness is what is going on.
Notice how nicely your "find . -type f -exec dos2unix {}" goes
down to .git/objects and eats your loose objects
You probably wanted to do
git ls-files | xargs dos2unix
instead.
next prev parent reply other threads:[~2007-11-15 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 21:50 New repo quickly corrupted Jason Sewall
2007-11-15 21:55 ` Junio C Hamano [this message]
2007-11-15 21:59 ` Jason Sewall
2007-11-15 22:01 ` Linus Torvalds
2007-11-15 22:06 ` Jason Sewall
2007-11-15 22:12 ` Nicolas Pitre
2007-11-15 22:37 ` Linus Torvalds
2007-11-16 5:45 ` Christian Couder
2007-11-16 7:35 ` Andreas Ericsson
2007-11-17 12:53 ` Christian Couder
2007-11-17 14:13 ` Robin Rosenberg
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=7vejer41ib.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jasonsewall@gmail.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).