Re: Advice on strategy for "temporary" commits

From: Alex Riesen <raa.lkml@gmail.com>
Date: Mar 8, 2007, 16:11 UTC
Message-ID: <81b0412b0703080811m27ff892eg5bf1cdf93f89051a@mail.gmail.com>
In-Reply-To: <e1dab3980703080639i4c553e89nb931c2aea45b023b@mail.gmail.com>

On 3/8/07, David Tweed <david.tweed@gmail.com> wrote:

Show 15 quoted lines

> I've been working with my system taking automatic
> hourly git snapshots of (filtered portions of) my home
> directory for a couple of months. Being able to look
> back to what files looked like mid-afternoon yesterday,
> or on 18 Nov, is proving modestly useful. However,
> I'm thinking about adding "temporary" commits every
> ten minutes which then get discarded after 5 hours-ish
> (in addition to the long-term archival hourly commits).
> This is motivated by the desire to have finer granularity
> for testing/bisecting short-term regressions but not having
> ridiculously fine-grained changes clogging up the
> archive long-term. (I'm aware that with the commits
> being primarily taken on a timed basis I'll have more
> non-compiling changes than is usual in a repository, so
> that this may not turn out to be useful in practice.)

Try using temporary and primary branch. Commit 10-minutes to the temporary branch, reset it to the head of primary branch after you did a commit to it and repack. Commits from temporary branch will be removed. You even can setup/modify your editor, to do a temporary commit every time you save a file, for extra ganularity.