Re: How to stop sharing objects between repositories

[Mike Galbraith <efault@gmx.de>]

On Mon, 2009-08-17 at 02:48 -0400, Jeff King wrote:
> On Mon, Aug 17, 2009 at 04:21:22AM +0200, Mike Galbraith wrote:
> 
> > >  (1) Such a user does not necessarily know a casual "git repack -a" breaks
> > >      the dependency, defeating the -s option s/he deliberately used in
> > >      order to save disk space in the first place.  Perhaps we can reword
> > >      this further to kill two penguins with a single stone?
> > 
> > Perhaps a runtime warning that you're about to break it?  This user may
> > not even be the one who set the thing up, no?
> 
> I'm not really sure what such a setup would look like. If it is a big
> hosting site like kernel.org or repo.or.cz, then probably it wouldn't
> matter much. The admins there should probably be running "git repack -l
> -d -A" periodically to consolidate the object stores (which can happen
> from this sort of repacking, or from people just pushing the same
> commits to their repos).
> 
> That being said, I can see there being setups where such a warning might
> be useful. However, we don't really know if the user _wants_ that
> effect, or if it is an accident. So people following the recommnded
> "here is how you break the dependency" advice will also get the warning.
> 
> I'm torn on whether this is actually a good idea.

Yeah.  There are any number of ways to shoot oneself in the foot, and
while on the one hand idiot proofing can be nice if you were about to
screw up, "really really?" messages are most frequently annoying noise.

	-Mike