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

Re: parsecvs fails even on simple input

From
Keith Packard <keithp@keithp.com>
Date
Jun 24, 2007, 21:31 UTC
Message-ID
<1182720667.13289.41.camel@neko.keithp.com>
In-Reply-To
<20070622113625.GD12473@rkagan.sw.ru>
On Fri, 2007-06-22 at 15:36 +0400, Roman Kagan wrote:
Show 5 quoted lines
> The problem is the following: after that commit parsecvs tries to add
> objects to the git tree on its own via calls to libgit; however, in
> between it runs git-pack-objects.  Thus objects move to pack files
> without libgit being aware of it; this results in 'ivalid object'
> errors.

Sticking a call to reprepare_packed_git() after the pack creation fixes this nicely.

>  Wouldn't it be better to teach parsecvs
> to speak git-fast-import language instead?
Avoiding fork/exec is rather important for parsecvs perforamance.
-- 
keith.packard@intel.com
Previous: Roman KaganNext: Shawn O. Pearce
Message 2 of 5 in “parsecvs fails even on simple input”
  1. Roman KaganJun 22, 2007
  2. Keith PackardJun 24, 2007
  3. Shawn O. PearceJun 25, 2007
  4. Roman KaganJun 27, 2007
  5. Keith PackardJun 27, 2007

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.