Re: [StGIT RFC PATCH] Don't use refs/bases/<branchname>

From: Karl Hasselström <kha@treskal.com>
Date: May 2, 2007, 06:50 UTC
Message-ID: <20070502065054.GA9919@diana.vm.bytemark.co.uk>
In-Reply-To: <e5bfff550705011259w567a98dj6d0a68b0fbe90994@mail.gmail.com>

On 2007-05-01 21:59:34 +0200, Marco Costalba wrote:

Show 10 quoted lines

> On 5/1/07, Karl Hasselström <kha@treskal.com> wrote:
>
> > (But if I were you, I'd look for the patches under patches/refs
> > anyway; they _have_ to be there to survive garbage collection, so
> > no amount of stgit refactoring will break qgit.)
>
> Well, I did. ;-)
>
> Actually I pushed a patch few hours ago to read patches sha under
> refs/patches.

Good. This was precisely what I was hoping to scare you into doing! :-)

Show 7 quoted lines

> The problem is that the patch (for now) is pushed only for the new
> development version of qgit, not the stable one and, worse, all the
> currently released versions will break if you remove
> <git dir>/patches/ directory.
>
> So please, if possible deprecate <git dir>/patches/ directory but do
> not remove for a while, so to let users to upgrade gracefully.

It's not near the top of my kill list by any stretch of the imagination, so no need to worry. And even if it were, Catalin would certainly stand as a wall of sanity between qgit and my chain saw. :-)

Thanks.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle