`arc` changes my commit messages

Yuras Shumovich shumovichy at gmail.com
Tue Oct 21 13:45:59 UTC 2014

On Tue, 2014-10-21 at 09:34 -0400, Richard Eisenberg wrote:
> Hi all,
> Is there a way to put `arc` into a read-only mode?

Not sure it is relevant, please ignore me if it is not.

Does "arc diff --preview" work for you? It will create a diff without
creating revision and changing anything locally. Then you can attach the
diff to an existent revision or create new one.

> Frequently while working on a patch, I make several commits, preferring to separate out testing commits from productive work commits and non-productive (whitespace, comments) commits. Sometimes each of these categories are themselves broken into several commits. These commits are *not* my internal workflow. They are intentionally curated by rebasing as I'm ready to publish the patch, as I think the patches are easy to read this way. (Tell me if I'm wrong, here!) I've resolved myself not to use `arc land`, but instead to apply the patch using git.
> Yet, when I call `arc diff`, even if I haven't amended my patch during the `arc diff`ing process, the commit message of the tip of my branch is changed, and without telling me. I recently pushed my (tiny, uninteresting) fix to #9692. Luckily, my last commit happened to be the meat, so the amended commit message is still wholly relevant. But, that won't always be the case, and I was surprised to see a Phab-ified commit message appear in the Trac ticket after pushing.
> I know I could use more git-ery to restore my old commit message. But is there a way to stop `arc` from doing the message change in the first place?
> Thanks!
> Richard
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs

More information about the ghc-devs mailing list