Advocacy vs. git

[Hans Meine]

On Tuesday 28 April 2009 16:01:35 Arne Babenhauserheide wrote:
> Am Dienstag 28 April 2009 13:09:00 schrieb Hans Meine:
> > It would be great if there was a way to keep track of "shared"
> > changesets, i.e. ones that I were already pushed or cloned, such that
> > editing them should be prohibited (or warned about).  AFAICS it's not
> > safely possible (in particular, anyone with a local login can clone my
> > world-readable repo without me knowing it), but when everyone
> > pushes/pulls to/from a shared central repo, it might be feasible (and
> > useful).
>
> Wouldn't it be possible to just assume that default-push is where we share
> changesets to, so we can call "outgoing" and treat all reported changesets
> as non-shared ones?

It's exactly what I was thinking about.  Of course, "outgoing" might be an 
expensive, long-running operation, but maybe an extension could cache the 
result.

Martin's concern about false positives does not convince me; the purpose 
should be to *warn* the user about changing history too far back.  I think the 
benefit far outweights a potential false warning.

Greetings,
  Hans