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

very slow cherry-pick'ing (old-2.6-bkcvs tree)

From
EZErez Zadok <ezk@cs.sunysb.edu>
Date
Sep 6, 2007, 23:51 UTC
Message-ID
<200709062351.l86NpnAK004807@agora.fsl.cs.sunysb.edu>

Our group maintains Unionfs on the latest -rc kernel, but we also maintain several backports going all the way to 2.6.9. Once we complete the development and testing of a feature/fix in -latest, we cherry-pick those commits to older backports, and test those. When I cherry-pick from -latest to my 2.6.{22,21,20,19,18} repositories, it works reasonably fast. But when I cherry-pick to my 2.6.9 tree, it runs about 20 times slower! Why? Is there anything I can do to inspect what's going on and perhaps speed up the cherry-picking process?

Some info:
My 2.6.{18,19,20,21,22} trees were cloned from
   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.<N>.y.git
My 2.6.9 tree, however, was cloned from
   git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/old-2.6-bkcvs.git

after which, I truncated the tree (git-reset) to Linus commit which read "Linux 2.6.9-final".

BTW, I first git-clone --bare to my git server, and then I clone from it to my test machine.

BTW2, I do git-repack and prune-packed every week.

Thanks, Erez.

Next: Shawn O. Pearce
Message 1 of 3 in “very slow cherry-pick'ing (old-2.6-bkcvs tree)”
  1. Erez ZadokSep 6, 2007
  2. Shawn O. PearceSep 7, 2007
  3. Johannes SixtSep 7, 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.