Hi Philip, Le 2022-05-12 à 08:11, Philip Oakley a écrit : > On 11/05/2022 02:47, Philippe Blain via GitGitGadget wrote: >> diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt >> index 63a2ef54493..22848f84bec 100644 >> --- a/Documentation/MyFirstContribution.txt >> +++ b/Documentation/MyFirstContribution.txt >> @@ -710,13 +710,61 @@ dependencies. `prove` also makes the output nicer. >> Go ahead and commit this change, as well. >> [[ready-to-share]] >> -== Getting Ready to Share >> +== Getting Ready to Share: Anatomy of a Patch Series > Shouldn't the title also include the magic word 'Contribution'? Otherwise the change below may look inconsistent. I don't think so. This section is to introduce "what is a patch series" to readers that might be reading the word "patch" in a software development context for the very first time. Patch series are how Git is developped, so the title here should include these words, I think. > >> You may have noticed already that the Git project performs its code reviews via >> emailed patches, which are then applied by the maintainer when they are ready >> -and approved by the community. The Git project does not accept patches from >> +and approved by the community. The Git project does not accept contributions from the next two words of this sentence are "from pull requests". People that are familiar with GitHub will probably have heard "contributions" in the context of GitHub "pull requests", but maybe not "patches". So that's why I changed the wording here. Thank you for your comments, Philippe.
