From: Alex Riesen Date: Tue, 06 Feb 2007 13:32:02 GMT Subject: Re: Deprecation/Removal schedule Message-ID: <81b0412b0702060532l31f88f64s812d2829f4d45844@mail.gmail.com> In-Reply-To: On 2/6/07, Johannes Schindelin wrote: > > Or just do no repack in the referenced repo. > > That is not the solution. > > The error in your setup is to _rely_ on data which just _might go away_! The data cannot "just" go away. I'll have to "go the data away" manually. > IOW do _not_ use an unreliable repository for --reference! Well, that being an accident, I see no way to follow your advice. > > Anyway, the discussion outlived its usefulness. > > I have what I wanted (git fsck --unreachable), and nobody can force > > me to repack my shared repo, so the issue does not exist for the original > > poster. > > Well, I think unless you understand that you do something really fragile, > the discussion did not yet outlive its usefulness. Yes, preacher.