From: Pierre Habouzit <madcoder@debian.org>
To: Andreas Ericsson <ae@op5.se>
Cc: 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:27:42 +0100 [thread overview]
Message-ID: <20071212162742.GE14538@artemis.madism.org> (raw)
In-Reply-To: <475FFFB7.4010102@op5.se>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Wed, Dec 12, 2007 at 03:35:19PM +0000, Andreas Ericsson wrote:
> Pierre Habouzit wrote:
> > So am I having crazy thoughts and should I throw my crack-pipe away ?
> >Or does parts of this mumbling makes any sense to someone ?
>
> 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.
Well if you disable the reflog on some repositories, those commands
will just be slow. But would still work.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-12-12 16:28 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
2007-12-12 16:27 ` Pierre Habouzit [this message]
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=20071212162742.GE14538@artemis.madism.org \
--to=madcoder@debian.org \
--cc=ae@op5.se \
--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;
as well as URLs for NNTP newsgroup(s).