{"thread":{"id":"3300","subject":"stg branch switch causes unnecessary recompilation","startedAt":"2006-02-11T13:07:27Z","lastAt":"2006-02-11T13:07:27Z","messageCount":1,"participants":["Andrey Borzenkov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"15919","messageId":"200602111607.27631.arvidjaar@newmail.ru","threadId":"3300","inReplyTo":null,"subject":"stg branch switch causes unnecessary recompilation","fromName":"Andrey Borzenkov","fromEmail":"arvidjaar@newmail.ru","sentAt":"2006-02-11T13:07:27Z","receivedAt":"2006-02-11T13:07:27Z","isPatch":false,"sender":{"key":"arvidjaar@newmail.ru","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n{pts/1}% stg version\nStacked GIT 0.8.1\ngit version 1.1.6\nPython version 2.4.2 (#2, Jan 30 2006, 18:33:58)\n[GCC 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1)]\n\n\nApparently stg branch is implemented as\n\n- - pop all patches\n- - do git checkout branch\n- - push all patches\n\nunfortunately it results in changing timestamp of all patched files causing \nsometimes long recompilations. What I just had was:\n\n- - I have several local patches for kernel that I keep in separate branches; I \nalso have one branch that I pick patches into and that I keep in sync with \nupstream.\n\n- - I pulled 2.6.15.4 stable and recompiled. In the process I noticed a trivial \nerror in one file\n\n- - I created new branch, put fix in there, switched to my main branch, picked \npatch and did make. It resulted in recompilation of *everything* that was \ntouched by *any* patch.\n\nSometimes it may be quite time consuming. Notice that git checkout does not \nhave this problem - it sets timestamp exactly to the one in index. It would \nbe nice if stg did the same.\n\nregards\n\n- -andrey\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.2 (GNU/Linux)\n\niD8DBQFD7eGPR6LMutpd94wRAmGEAJ49maPpI6VjGyp8sIOwPBKQNuUeZgCePOoN\nC9bqat7QEA5Pt6bzegW0q2E=\n=0JHo\n-----END PGP SIGNATURE-----\n"}]}