@@ -574,7 +574,7 @@ zealous, inclusive and tireless maintainer that follows below._
574
574
< https://lore.kernel.org/git/[email protected] / >
575
575
is one of the most important design discussion in the early days of
576
576
Git. In that article, Linus outlines how his "ideal" SCM tool would
577
- let you follow the historyz of a single function in today's codebase
577
+ let you follow the history of a single function in today's codebase
578
578
backwards, notice that at certain revision the function appeared, but
579
579
the tool finds five functions disappeared in the same revision, all
580
580
looking very similar to the function we are interested in that was
@@ -611,10 +611,10 @@ zealous, inclusive and tireless maintainer that follows below._
611
611
responsibility. The maintainer may play a role of the final arbiter,
612
612
but it would be great if we can come up with a mechanism to allow list
613
613
participants to bear more of the burden of picking and choosing good
614
- direction to go, deciding if a particular change is worth doing or the
615
- are better ways to do the same thing, etc. I've been trying to nudge
616
- the list discussions in that direction for the past few years, but
617
- without much success, I think.
614
+ direction to go, deciding if a particular change is worth doing or
615
+ are there better ways to do the same thing, etc. I've been trying to
616
+ nudge the list discussions in that direction for the past few years,
617
+ but without much success, I think.
618
618
619
619
620
620
## Other News
0 commit comments