Mike Hommey wrote:
On Wed, Dec 12, 2007 at 04:35:19PM +0100, Andreas Ericsson <ae@xxxxxx> 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@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
