Re: Git drawbacks?

From: Dmitry Smirnov <divis1969@gmail.com>
Date: Nov 10, 2009, 14:14 UTC
Message-ID: <loom.20091110T150242-922@post.gmane.org>
In-Reply-To: <20091110134540.GK27126@dpotapov.dyndns.org>

Dmitry Potapov <dpotapov <at> gmail.com> writes:

Show 9 quoted lines

> I am not sure I understood your question. What 'git archive' does is to
> create a tar or zip archive or any version that you specify. So, you can
> use it to export the snapshot of any version to a temporary directory
> for testing if this testing takes a noticeable time and you want to be
> able to work on something else in meanwhile. If necessary, you can
> create a temporary branch starting at the intesting point and to add
> some commits there (such as a new test case to reproduce the problem)
> and then run test on it. Later, you can either rebase or merge these
> commits to any branch that needs them.

Ok, I got it. So the scenario is something like that:
1. Stash or commit my current changes
2. Sync (reset or checkout) to some other version/branch
3. Create temporary branch 
4. Edit and Commit
5. "git archive" to get snapshot
6. Get back to original change

This looks reasonable. Until you need to correct the fix and test it again.

Perhaps, I have to explain why fix/test cycle is so long. I'm working on mobile platform development. It is not so modular, so I need to build the whole image, then flash the mobile and test it in a real network. This takes much time and need much disk space (about 2GB of source files. In fact, significant number of these files are not needed for the build, but it is too hard to force CM engineers to fix this :-) )