3 ms·
> History rewrite sounds like a dirty thing well you're only rewriting local history, so you're a-ok. history re-writing becomes a dirty word when you re-write
by dustingetz 16y ago
> History rewrite sounds like a dirty thing
well you're only rewriting local history, so you're a-ok. history re-writing becomes a dirty word when you re-write history that someone else may have already seen. i know you already know this.
- 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.