From: Dave Zarzycki <zarzycki@apple.com>
Date: Tue, 21 Feb 2012 23:59:38 GMT
Subject: Re: [RFC] pre-rebase: Refuse to rewrite commits that are reachable from upstream
Message-ID: <1AD297DA-6E85-4808-94F8-907BA890E7F6@apple.com>
In-Reply-To: <7vsji3eoqs.fsf@alter.siamese.dyndns.org>


On Feb 21, 2012, at 6:43 PM, Junio C Hamano <gitster@pobox.com> wrote:

> Johan Herland <johan@herland.net> writes:
> 
>> history"[1], but won't cause any false positives (and small enough
>> false negatives). If there really is no way to implement this, then we
>> shouldn't give users false hopes by putting it in the survey...
> 
> I think that question should be "warn before pushing out a commit that the
> user may later regret to have pushed out" ;-)

Why limit this proposal to just the commits that are reachable from upstream? What if somebody pulls from your repo?

In other words, wouldn't it be better to have a git track "unshared" commits and only let those be rewritten? The theory being that if the given commits haven't been pushed or pulled anywhere, then they are safe to rewrite.

davez