That revi, here and there. Maybe also somewhere else too. Also somewhere intranet.
- How to pronounce the nick: lɛbi (TTS generated sounds)
- What time is it for revi?
Profile image: © 2022 (Anonymous) All Right Reserved. Used with permission.
That revi, here and there. Maybe also somewhere else too. Also somewhere intranet.
Profile image: © 2022 (Anonymous) All Right Reserved. Used with permission.
One weird observation:
From the text body:IMPORTANT: Share that patch to your DBA <snip>
It's 3 days past the scheduled execution date but the settings in dashboard and docs are still there.
BTW: You can use commit hash in place of branch name in URL, to set link to display specific file at the time of that commit, in this case https://github.com/unicode-org/cldr/blob/9d96f340ab145003b3e6d12d95ffb16f19a8a529/common/supplemental/windowsZones.xml. I'm not gonna update commit message, though. (so you can do it when landing? :P)
removing from review queue until the underlying task discussion is settled.
$ git show commit d519f75dfdee61bb109468aa708c47f53f3e5128 (HEAD -> stable, origin/stable) Author: Mark Jervelund <EMAIL-REDACTED> Date: Mon Feb 12 11:51:24 2024 +0100
I'm pretty fine with DCO (which I already do every commit via the git commit -s command) — but I'd rather not sign a CLA. (I’m pretty undecided if I will sign phorge's CLA, but phorge is not commercial entity seeking to mongodb/terraform/elasticsearch-ize the software (read: make a profit from open source, then turn it into All Rights Reserved) so I might do so… after all these incidents I'm rather wary of it.)
git config --global core.quotepath false
Posted question at git@vger.kernel.org.
X-Spam-known-sender: no X-Spam-sender-reputation: 500 (none) X-Spam-score: 0.8 X-Spam-hits: BAYES_50 0.8, ME_SENDERREP_NEUTRAL 0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001, SPF_HELO_PASS -0.001, SPF_PASS -0.001, LANGUAGES en, BAYES_USED user, SA_VERSION 3.4.6 X-Spam-source: IP='198.74.57.92', Host='secure.phorge.dev', Country='US', FromHeader='dev', MailFrom='dev' X-Spam-charsets: plain='utf-8'
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.
Yeah, on my todo list for the weekend.
And my spam filter says:
Something I stumbled upon few months ago (via forgejo): agit-flow[^1]. Maybe worth sharing here -- for teh record? It does have some CLI client (git-repo) but it's optional and push via git push origin HEAD:refs/for/<target-branch>/<session> would trigger the Code Review process, without gerrit's Change-Id hack.
Haven't tested yet, I was just trying to document the patch behavior.
That is, what I get from setup issues at https://issuetracker.revi.xyz/config/issue/deprecations/ is to report it:
For completeness: Cf. T15808#17058
Also, phorge version and arcanist version is included in line 2.
Or wrap a text with a background color - (something like What if I can change the background color here (and no italics)?)
For the sake of completeness: Please add mention of rPd519f75dfdee61bb109468aa708c47f53f3e5128. Thanks!
I probably missed the train, so… can you add the docs for this? :-P
I was responding to the previous comment which...
Can this (I mean rPb445e1d80df9 )be backported into stable?
GitHub/Facebook is already supported as a Login/Registration providers.
Probably my somewhat 10 cents at a broader level;
In D25573#16505, @aklapper wrote:Thanks! Definitely way more correct :) Feel free to arc land
As far as fonts are concerned, while we should decide on a new default font, should this be a configurable? Should we make an item (in Config for defaults, and in Settings for users' choice) to change the UI font on an installation?
That should be easy given all files until this week… is all doomed. <_<.
Hey, the result of the commands:
Sorry for the late reply; was busy IRL.
In T15035#1019, @TitanNano wrote:Are there any thoughts about a matrix channel? It would also be possible to bridge it to IRC.