2 ms·
> history re-writing becomes a dirty word when you re-write history that someone else may have already seen. It seems like git (or some friendlier wrapper) cou
by cpeterso 16y ago
> history re-writing becomes a dirty word when you re-write history that someone else may have already seen.
It seems like git (or some friendlier wrapper) could track this for you. For example, if you've pushed changes to a remote repo, then git could mark those changes as "published" in your local repo and warn you when you later try to rewrite that branch's history.