From: Andrey Borzenkov <arvidjaar@newmail.ru>
To: git@vger.kernel.org
Subject: stg branch switch causes unnecessary recompilation
Date: Sat, 11 Feb 2006 16:07:27 +0300 [thread overview]
Message-ID: <200602111607.27631.arvidjaar@newmail.ru> (raw)
-----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-----
reply other threads:[~2006-02-11 13:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602111607.27631.arvidjaar@newmail.ru \
--to=arvidjaar@newmail.ru \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox