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

Re: [PATCH] Script for automated historical Git tree grafting

From
Petr Baudis <pasky@ucw.cz>
Date
Apr 8, 2006, 03:09 UTC
Message-ID
<20060408030936.GN27631@pasky.or.cz>
In-Reply-To
<20060406175246.3bd1c972.akpm@osdl.org>

Dear diary, on Fri, Apr 07, 2006 at 02:52:46AM CEST, I got a letter where Andrew Morton <akpm@osdl.org> said that...

Show 7 quoted lines
> Petr Baudis <pasky@suse.cz> wrote:
> >
> > This script enables Git users to easily graft the historical Git tree
> >  (Bitkeeper history import) to the current history.
> 
> What impact will that have on the (already rather poor) performance of
> git-whatchanged, gitk, etc?
Negative. ;-)

I didn't try gitk myself, but according to Nick Riviera it eats 1.6G... Otherwise, assuming that you have at least git-1.2.5, git-whatchanged on the whole tree should be roughly equally fast as it was before grafting, but git-whatchanged on individual paths is _significantly_ slower.

That said, 1.3.0rc2 should already have Linus' optimization which should fix or at least mitigate the performance hit on narrowed-down git-whatchanged.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time.  I think
I have forgotten this before.
Next: Nicholas Miell
Message 1 of 2 in “Re: [PATCH] Script for automated historical Git tree grafting”
  1. Petr BaudisApr 8, 2006
  2. Nicholas MiellApr 8, 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.