From: Andreas Ericsson <ae@op5.se>
To: Mike Hommey <mh@glandium.org>
Cc: Pierre Habouzit <madcoder@debian.org>, Git ML <git@vger.kernel.org>
Subject: Re: [(not so) random thoughts] using git as its own caching tool
Date: Wed, 12 Dec 2007 17:03:00 +0100 [thread overview]
Message-ID: <47600634.3030207@op5.se> (raw)
In-Reply-To: <20071212154848.GA19294@glandium.org>
Mike Hommey wrote:
> On Wed, Dec 12, 2007 at 04:35:19PM +0100, Andreas Ericsson <ae@op5.se> wrote:
>> A bit of both ;-)
>>
>> I like the idea to use the git object store, because that certainly
>> has an API that can't be done away with by user config. The reflog
>> and its expiration mechanism is subject to human control though, and
>> everyone doesn't even have them enabled. I don't for some repos where
>> I know I'll create a thousand-and-one loose objects by rebasing,
>> --amend'ing and otherwise fiddling with history rewrites.
>>
>> Having a tool that works on some repos but not on others because it
>> relies on me living with an auto-gc after pretty much every operation
>> would be very tiresome indeed.
>
> There is already a tool that relies on reflogs: stash.
>
No, "git stash save" works anyway. It's when you want to use multiple
stashes that it becomes tricky, but even that works if you're willing
to put some effort into it (although I don't use stash a lot, and not
at all in the very rebase-heavy ones).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-12-12 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 0:38 [(not so) random thoughts] using git as its own caching tool Pierre Habouzit
2007-12-12 6:51 ` Mike Hommey
2007-12-12 15:35 ` Andreas Ericsson
2007-12-12 15:48 ` Mike Hommey
2007-12-12 16:03 ` Andreas Ericsson [this message]
2007-12-12 16:27 ` Pierre Habouzit
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=47600634.3030207@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=mh@glandium.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;
as well as URLs for NNTP newsgroup(s).