From: Simon Ruderich <simon@ruderich.org>
To: Matthias Beyer <mail@beyermatthias.de>
Cc: git@vger.kernel.org
Subject: Re: File extension conflict when working with git and latex
Date: Fri, 21 Mar 2014 17:36:28 +0100 [thread overview]
Message-ID: <20140321163628.GA28121@ruderich.org> (raw)
In-Reply-To: <20140321161324.GC2965@fu.192.168.200.1>
On Fri, Mar 21, 2014 at 05:13:24PM +0100, Matthias Beyer wrote:
> Unfortunetely, we wrote our `make clean` task recursively. I think you
> can imagine what went wrong: The clean-task corrupted the repository,
> as it removed .idx files from within .git/.
>
> I lost work because of this ugly name collision.
Hello Matthias,
You can recreate the .idx files by running
git index-pack .git/objects/pack/pack-<hash>.pack
for each pack file.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
next prev parent reply other threads:[~2014-03-21 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 16:13 File extension conflict when working with git and latex Matthias Beyer
2014-03-21 16:36 ` Simon Ruderich [this message]
2014-03-21 16:46 ` Matthias Beyer
2014-03-21 17:01 ` Simon Ruderich
2014-03-21 18:32 ` Junio C Hamano
2014-03-21 21:31 ` Michael Haggerty
2014-03-22 7:11 ` Torsten Bögershausen
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=20140321163628.GA28121@ruderich.org \
--to=simon@ruderich.org \
--cc=git@vger.kernel.org \
--cc=mail@beyermatthias.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.