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

Re: [PATCH v0] fast-import: Add drop command

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Oct 27, 2011, 11:06 UTC
Message-ID
<CAGdFq_iY92Gc=WLFVVMpi8w5JNZMo5bSk5=wjHyCmjXmP4RXrQ@mail.gmail.com>
In-Reply-To
<CAOpHH-VEhtOg6ai5p9VxWBKA3AFpG3meiJVGrWR4j68ffyQ6Bg@mail.gmail.com>
Heya,
On Tue, Oct 25, 2011 at 11:56, Vitor Antunes <vitor.hda@gmail.com> wrote:
Show 21 quoted lines
> On Mon, Oct 24, 2011 at 7:01 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> I for one welcome our new branch deleting overlords :).
>>
>> You mention that checkpointing solves some of the concerns raised by
>> others in this thread, would automatic checkpointing be way to make
>> sure everything is as it should be?
>
> Apparently I did not explain myself correctly. Let me try again :)
>
> This is what I am doing:
>
> 1) import topic
> 2) checkpoint
> 3) diff-tree and processing
> 4) exit if processing returns ok
> 5) reset topic to another HEAD
> 6) goto 1)
>
> In this scenario it is the checkpoint that "breaks" everything because
> it will write the original tree to disk. When fast-import exits it will
> find the old tree on disk but not within "topic" tree.

I'm afraid I don't understand why it's a bad thing that fast-import will find the old tree on disk, won't it just be gc-ed if it is no longer used?

-- 
Cheers,

Sverre Rabbelier
Previous: Vitor AntunesNext: Vitor Antunes
Message 9 of 15 in “fast-import: Add drop command”
  1. fast-import: Add drop commandVitor Antunes, Sep 24, 2011
  2. fast-import: Add drop commandVitor Antunes, Sep 24, 2011
  3. Jonathan NiederSep 24, 2011
  4. Dmitry IvankovSep 24, 2011
  5. Vitor AntunesSep 27, 2011
  6. Vitor AntunesOct 24, 2011
  7. Sverre RabbelierOct 24, 2011
  8. Vitor AntunesOct 25, 2011
  9. Sverre RabbelierOct 27, 2011
  10. Vitor AntunesOct 27, 2011
  11. Sverre RabbelierOct 27, 2011
  12. Vitor AntunesNov 9, 2011
  13. Sverre RabbelierNov 9, 2011
  14. Vitor AntunesNov 9, 2011
  15. Vitor AntunesSep 24, 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.