I use git arc stage to update the commit messages which adds the URL and Reviewed by using the format of FreeBSD's commit template instead of the format arcanist prefers. I think this will be a better fix (unlike arc land you can git arc stage an entire patch series and then do a single git push).

The reason I want this is so that arc diff HEAD^ adds the URL to the commit message. Then I can just add more commits and do arc diff HEAD^^ too update the review.

Never used arc land, but LLVM has patched their phabricator instance so that arc patch --nobranch gives me a sane commit message.

FYI the LLVM fix is https://github.com/joker-eph/phabricator/commit/5d531bc2532d4a87b49e8139c4233c1d72b1ec8b

Workaround: arc set-config --local history.immutable false. However that won't work if you have a git worktree :( To work around that you need to patch arcanist since upstream doesn't want any contributions (https://secure.phabricator.com/D21438)

In D27971#632293, @arichardson wrote:

Workaround: arc set-config --local history.immutable false. However that won't work if you have a git worktree :( To work around that you need to patch arcanist since upstream doesn't want any contributions (https://secure.phabricator.com/D21438)

I haven't had time to check this, but if we really need to patch arc, we can patch it locally in ports.

In D27971#632295, @lwhsu wrote:

In D27971#632293, @arichardson wrote:

Workaround: arc set-config --local history.immutable false. However that won't work if you have a git worktree :( To work around that you need to patch arcanist since upstream doesn't want any contributions (https://secure.phabricator.com/D21438)

I haven't had time to check this, but if we really need to patch arc, we can patch it locally in ports.

If we want FreeBSD cross-development to become a fully supported flow -- e.g., cross build, cross debug, emulate in Qemu, etc -- then we need to avoid patches being added in ports builds, since those won't be available on a non-FreeBSD development system (e.g., on Linux, Mac OS X, etc). Unless we also maintain and make available adapted versions there, and I'm not sure we want to be in that business...?

In D27971#659501, @rwatson wrote:

If we want FreeBSD cross-development to become a fully supported flow -- e.g., cross build, cross debug, emulate in Qemu, etc -- then we need to avoid patches being added in ports builds, since those won't be available on a non-FreeBSD development system (e.g., on Linux, Mac OS X, etc). Unless we also maintain and make available adapted versions there, and I'm not sure we want to be in that business...?

We don't want to be in the business of providing Windows / mac OS installers for patched Phabricator, indeed. However, I think it's fine to tell folks to either use our fork of arc (obtaining from GitHub etc.), or accept the caveats such as lack of support for worktrees.

ping? Can we drop the immutable setting so that arc diff adds the Differential Revision: metadata to commit messages automatically?