On 2008-06-16 18:18:40 +0200, Sverre Rabbelier wrote:

quoted text
> On Mon, Jun 16, 2008 at 5:57 PM, Pierre Habouzit <madcoder@debian.org> wrote:
>
> > On Mon, Jun 16, 2008 at 03:48:51PM +0000, Pierre Habouzit wrote:
> >
> > > Actually it would be rather straightforward to put it in the
> > > usual git store, and represent the current rr-cache with a flat
> > > file that points to the in-git preimage/postimages, and make
> > > git-gc aware of those.
> >
> > Actually, this is probably a required step in the direction of
> > sharing such things btw.
>
> Perhaps an approach similar to the 'notes' implementation can be
> used, in which a separate branch is created to contain the notes.
> This way the rerere information (being the 'rerere' branch) can be
> shared easily (by just pulling the branch), and as said we get free
> compression. Another advantage would be that you automagically get
> the ability to unlearn a bad rerere by simply (partially) reverting
> a commit on the rerere branch!

FWIW, StGit is well on its way to store its patch metadata in a git
branch, for much the same reasons.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html