Probably not enough consensus for a mass edit. Best we can do is case-by-case fixes reading warn reports.

Uh!

I see. So, is that functionality already a part of arc diff? In other words, if arc work T123 would have worked exactly the same way as arc work branch-name (by creating a branch that's called either T123 or branch-name), then arc diff would correctly link it?

Yes - it works seamlessly because if the local branch has a task number in it, the diff is automatically linked to that task when you run arc diff

I'd assume that it also links the task and the diff together and optionally allows to close the task automatically on diff land?

Just adding references

OK. Well, thaanks \o/

In T15872#18251, @valerio.bozzolan wrote:

About this:

unset LC_ALL + LC_MESSAGES=C

I think it's not safe since other LC_STUFF can still be read 🤔

About this:

This [LANG=C] is supposed to be the default for missing LC_stuff

OK thanks! you persuaded me

LC_ALL=C is not risky on GNU systems.

git config --global core.quotepath false

Posted question at git@vger.kernel.org.

I also faced this, tested @ D25623, and found out git format-patch was emitting that result which causes git apply to fail. See this git format-patch example.

In T15096#12185, @valerio.bozzolan wrote:

Another problem dramatically frequent for newcomers (at least in my office).

It's relatively too much easy to start with a similar commit message:
...

At least, please go to GitLab, instead of GitHub, so at least you use Free Software :)

Just some (probably final) thoughts on arcanist and phabricator/phorge. After quite a bit of discussion internally, we are moving on to GitHub with our repositories (which were previously stored in another Git server - not Phabricator). But that move also spells the end for our/my 10+ year long use of Phabricator, because when we move to GitHub, we'll also be ditching Phabricator for code reviews.

Since Subversion allows to checkout just a sub-directory,

Maybe we can wontfix this, and try other more modern approaches like flatpak. Example:

6 year old in-your-face unreported bugs like these make me wonder how many people use Phabricator/Phorge :-(

It's not many, but this issue would be specific to anyone using Phabricator/Phorge for PHP development, which is likely Phab/Phorge itself is close to 100% of that market. And Phab/Phorge also itself has its own unit testing framework instead of PHPUnit.

As an aside, what do you think of https://github.com/campbsb/example-phorge-php-project - should we put a selection of example projects on https://we.phorge.it, either as individual repos, or one repo containing a bunch of examples, or somewhere in the arcanist repo ?

More complete test case added to D25472 which demonstrates the following error:

In T15667#14211, @Sten wrote:

how many people use Phabricator/Phorge :-(

I guess the documentation needs an update on page https://we.phorge.it/book/phorge/article/arcanist_lint_unit/ and/or https://we.phorge.it/book/phorge/article/arcanist_new_project/

6 year old in-your-face unreported bugs like these make me wonder how many people use Phabricator/Phorge :-(