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

Re: parsecvs and unnamed branches

From
PRPavel Roskin <proski@gnu.org>
Date
Jun 17, 2006, 04:35 UTC
Message-ID
<1150518950.9144.17.camel@dv>
In-Reply-To
<9e4733910606162115g2165212bgf32a2e328cce751a@mail.gmail.com>
On Sat, 2006-06-17 at 00:15 -0400, Jon Smirl wrote:
> I had already caught that one, the fix was a few mails back.
> git_dir is an atom and shouldn't be freed with free.

I see it now. My patch was wrong - there is another free(git_dir) in the same function. Keith, please remove both.

> After five hours I hit this:
> fprintf (stderr, "Error: branch cycle\n");

This is more like a logical error. Maybe you actually have circling branches due to causality violations or something :-)

Sure, Valgrind would be still useful to make sure it's not something mundane.

-- 
Regards,
Pavel Roskin
Previous: Jon SmirlNext: Keith Packard
Message 11 of 14 in “parsecvs and unnamed branches”
  1. Jon SmirlJun 16, 2006
  2. Keith PackardJun 16, 2006
  3. Jon SmirlJun 16, 2006
  4. Jon SmirlJun 16, 2006
  5. Keith PackardJun 16, 2006
  6. Jon SmirlJun 17, 2006
  7. Pavel RoskinJun 17, 2006
  8. Jon SmirlJun 17, 2006
  9. Pavel RoskinJun 17, 2006
  10. Jon SmirlJun 17, 2006
  11. Pavel RoskinJun 17, 2006
  12. Keith PackardJun 17, 2006
  13. Jon SmirlJun 17, 2006
  14. Keith PackardJun 17, 2006

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.