Re:Brian Kernighan adds Unicode support to Awk
by bzxcvbn on Sunday August 21, 2022 @03:51PM
(#32543759)
What happens if multiple people contribute on the same PR (which is extremely common)? With a patch, that history is lost.
Re:Brian Kernighan adds Unicode support to Awk
by rtpg on Sunday August 21, 2022 @09:34PM
(#32546334)
I mean… you can imagine a history being stiched together serverside. The ingest mechanism isn’t the final result. Just that “have to make a PR, have to make a branch name, etc” feels a bit silly
Re:Brian Kernighan adds Unicode support to Awk
by bzxcvbn on Monday August 22, 2022 @02:05AM
(#32547896)
> I mean… you can imagine a history being stiched together serverside.
And since Git has a builtin mechanism for tracking such things, called branches, we could ask users to create a new one. Then add a possibility for people to comment on the proposed change. Sounds like you're incrementally reinventing PRs.
Re:Brian Kernighan adds Unicode support to Awk
by rtpg on Monday August 22, 2022 @05:25AM
(#32549185)
But _we don't need to ask users to do this_. We can just do "the obvious thing".
We're talking about usability here, of course the fundamental features are available in Git. It's Git!
Here [0] is a more well written out version of this idea (by a developer of Mercurial).
[0] https://gregoryszorc.com/blog/2020/01/07/problems-with-pull-...
Re:Brian Kernighan adds Unicode support to Awk
by sargstuff on Sunday August 21, 2022 @10:27PM
(#32546639)
Oh, thought being told to git solved the conflicts.
Re:Brian Kernighan adds Unicode support to Awk
by Blikkentrekker on Monday August 22, 2022 @05:31PM
(#32557552)
Of course not, the email can list the contributors, or not as it's own pleasure.
The fact that (for example) GitHub requires a fork for you to send a PR to a project (that you don’t have push access to) is soooo overkill.