git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: File extension conflict when working with git and latex

From
Simon Ruderich <simon@ruderich.org>
Date
Mar 21, 2014, 17:01 UTC
Message-ID
<20140321170142.GA30418@ruderich.org>
In-Reply-To
<20140321164651.GD2965@fu.192.168.200.1>
On Fri, Mar 21, 2014 at 05:46:51PM +0100, Matthias Beyer wrote:
Show 9 quoted lines
> Hi Simon,
>
> I think so. I executed:
>
>     git fsck # reports N missing blobs, commits, trees and dangling stuff
>     git index-pack ...
>     git fsck # reports only dangling commits and blobs
>
> I don't know if this means that the repository is fixed now?
Hello Matthias,

If nothing else was deleted, then yes, the repository should be fine now.

Regards Simon

-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Previous: Matthias BeyerNext: Junio C Hamano
Message 4 of 7 in “File extension conflict when working with git and latex”
  1. Matthias BeyerMar 21, 2014
  2. Simon RuderichMar 21, 2014
  3. Matthias BeyerMar 21, 2014
  4. Simon RuderichMar 21, 2014
  5. Junio C HamanoMar 21, 2014
  6. Michael HaggertyMar 21, 2014
  7. Torsten BögershausenMar 22, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.