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

Re: [ANNOUNCE] Cogito-0.18.2

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Nov 17, 2006, 01:44 UTC
Message-ID
<46a038f90611161744q6c535218n5b815ef1fc5228b6@mail.gmail.com>
In-Reply-To
<20061117004930.GC7201@pasky.or.cz>
On 11/17/06, Petr Baudis <pasky@suse.cz> wrote:
Show 5 quoted lines
> * cg-log does not follow history across renames anymore; it never really
>   actually worked and was instead causing problems and random error
>   messages. There needs to be git-core support for this funcionality,
>   hacking it with a perl filter is bad design, so I'm not going to fix
>   the filter (but I'd take patches if someone else did ;).

I was looking at the follow renames Perl script last week (hey, I was bored!) and while I could tell it didn't work, I did get the feeling that it wasn't an impossible task, at least for the 'explicit paths' case. For the 'whole tree' and subpath cases it _is_ tricky, and would be faster to solve within git, but not impossible.

And even then, I am tempted to think that git log could provide some better hints than it does today when walking the whole tree or subpaths, so that cg-log or gitk can ask [if relevant] for selective rename info.

I am curious as to why you see it as bad design...
cheers,
Previous: Petr BaudisNext: Petr Baudis
Message 2 of 3 in “[ANNOUNCE] Cogito-0.18.2”
  1. Petr BaudisNov 17, 2006
  2. Martin LanghoffNov 17, 2006
  3. Petr BaudisNov 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.