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

stg branch switch causes unnecessary recompilation

From
ABAndrey Borzenkov <arvidjaar@newmail.ru>
Date
Feb 11, 2006, 13:07 UTC
Message-ID
<200602111607.27631.arvidjaar@newmail.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

{pts/1}% stg version Stacked GIT 0.8.1 git version 1.1.6 Python version 2.4.2 (#2, Jan 30 2006, 18:33:58) [GCC 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1)]

Apparently stg branch is implemented as
- - pop all patches
- - do git checkout branch
- - push all patches

unfortunately it results in changing timestamp of all patched files causing sometimes long recompilations. What I just had was:

- - I have several local patches for kernel that I keep in separate branches; I 
also have one branch that I pick patches into and that I keep in sync with 
upstream.
- - I pulled 2.6.15.4 stable and recompiled. In the process I noticed a trivial 
error in one file
- - I created new branch, put fix in there, switched to my main branch, picked 
patch and did make. It resulted in recompilation of *everything* that was 
touched by *any* patch.

Sometimes it may be quite time consuming. Notice that git checkout does not have this problem - it sets timestamp exactly to the one in index. It would be nice if stg did the same.

regards
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD7eGPR6LMutpd94wRAmGEAJ49maPpI6VjGyp8sIOwPBKQNuUeZgCePOoN C9bqat7QEA5Pt6bzegW0q2E= =0JHo -----END PGP SIGNATURE-----

Message 1 of 1 in “stg branch switch causes unnecessary recompilation”
  1. Andrey BorzenkovFeb 11, 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.