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

Re: Recovering from a bad object

From
jonsmirl@gmail.com <jonsmirl@gmail.com>
Date
Sep 18, 2011, 19:48 UTC
Message-ID
<CAKON4OzCYEQzKXwsNE59a-SOCHp=xibwk9oPmHs3_hMHCLaybg@mail.gmail.com>
In-Reply-To
<20110918193116.GB6334@nibiru.local>
On Sun, Sep 18, 2011 at 3:31 PM, Enrico Weigelt <weigelt@metux.de> wrote:
Show 23 quoted lines
> * Junio C Hamano <gitster@pobox.com> wrote:
>
>> > The object is likely at kernel.org.
>> > Can git go fetch it somehow?
>>
>> The protocol is designed specifically to disallow "I guessed that the
>> trade secret is contained within an object whose object name is this,
>> please feed me that object" kind of requests, so in general no.
>
> Maybe the local side (in some special repair mode) could check if
> some of the remote refs (and their referenced graphs) are broken
> and refetch them completely. If the remote side(s) got the objects
> you're missing (visibile to you), you'll be done after that.
>
> For example:
>
> A local branch "foo" is based on origin/master, somewhere in the
> line behind origin/master some objects are broken:
>
> It would find out that origin/master points to broken/missing objects
> and refetch it completely afresh (same as it would if they had never
> been fetched yet).
>
That's describes the lines I was thinking along.
Show 23 quoted lines
>
> Perhaps it's not that hard to implement: just requires a special
> git-fetch operation mode that ignores locally existing objects,
> and a few lines of shell code that simply fetches the whole remote
> to some temporary namespaces (and drop that when done). Ends up in
> the same traffic as a fresh clone, but at least runs automatically.
>
>
> cu
> --
> ----------------------------------------------------------------------
>  Enrico Weigelt, metux IT service -- http://www.metux.de/
>
>  phone:  +49 36207 519931  email: weigelt@metux.de
>  mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
> ----------------------------------------------------------------------
>  Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Enrico Weigelt
Message 7 of 7 in “Recovering from a bad object”
  1. jonsmirl@gmail.comMay 21, 2011
  2. Junio C HamanoMay 22, 2011
  3. jonsmirl@gmail.comMay 22, 2011
  4. jonsmirl@gmail.comMay 22, 2011
  5. Junio C HamanoMay 23, 2011
  6. Enrico WeigeltSep 18, 2011
  7. jonsmirl@gmail.comSep 18, 2011

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.