From: Philippe Blain <levraiphilippeblain@gmail.com> To: Philip Oakley <philipoakley@iee.email>, Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>, git@vger.kernel.org Cc: Emily Shaffer <emilyshaffer@google.com>, Johannes Schindelin <Johannes.Schindelin@gmx.de>, Victoria Dye <vdye@github.com>, Eric Sunshine <sunshine@sunshineco.com> Subject: Re: [PATCH v2 1/5] MyFirstContribution: add "Anatomy of a Patch Series" section Date: Thu, 12 May 2022 18:53:28 -0400 [thread overview] Message-ID: <bc0e05b4-f185-5aa2-ee3a-cb7278fa6ab9@gmail.com> (raw) In-Reply-To: <a901e47d-79cd-8d23-8c6c-de6299716eca@iee.email> 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.
next prev parent reply other threads:[~2022-05-12 22:53 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-27 19:04 [PATCH 0/3] Improve MyFirstContribution's GitGitGadget section Philippe Blain via GitGitGadget 2022-04-27 19:04 ` [PATCH 1/3] MyFirstContribution: move cover letter description to a separate file Philippe Blain via GitGitGadget 2022-04-27 21:15 ` Eric Sunshine 2022-04-27 22:02 ` Philippe Blain 2022-04-27 21:48 ` Junio C Hamano 2022-04-28 18:16 ` Philippe Blain 2022-04-27 19:04 ` [PATCH 2/3] MyFirstContribution: also explain cover letter in GitGitGadget section Philippe Blain via GitGitGadget 2022-04-27 20:43 ` Victoria Dye 2022-04-28 18:21 ` Philippe Blain 2022-04-29 16:27 ` Victoria Dye 2022-05-10 23:45 ` Philippe Blain 2022-04-27 19:04 ` [PATCH 3/3] MyFirstContribution: drop PR description for GGG single-patch contributions Philippe Blain via GitGitGadget 2022-04-27 21:56 ` Junio C Hamano 2022-04-28 18:25 ` Philippe Blain 2022-04-28 19:43 ` Junio C Hamano 2022-05-11 1:47 ` [PATCH v2 0/5] Improve MyFirstContribution's GitGitGadget section Philippe Blain via GitGitGadget 2022-05-11 1:47 ` [PATCH v2 1/5] MyFirstContribution: add "Anatomy of a Patch Series" section Philippe Blain via GitGitGadget 2022-05-11 6:20 ` Bagas Sanjaya 2022-05-11 21:30 ` Junio C Hamano 2022-05-11 21:48 ` Philippe Blain 2022-05-11 22:09 ` Junio C Hamano 2022-05-12 23:00 ` Philippe Blain 2022-05-12 12:11 ` Philip Oakley 2022-05-12 22:53 ` Philippe Blain [this message] 2022-05-11 1:47 ` [PATCH v2 2/5] MyFirstContribution: add standalone section on cover letter Philippe Blain via GitGitGadget 2022-05-11 10:01 ` Junio C Hamano 2022-05-11 21:49 ` Philippe Blain 2022-05-11 1:47 ` [PATCH v2 3/5] MyFirstContribution: reference "The cover letter" in "Preparing Email" Philippe Blain via GitGitGadget 2022-05-11 1:47 ` [PATCH v2 4/5] MyFirstContribution: reference "The cover letter" in GitGitGadget section Philippe Blain via GitGitGadget 2022-05-11 1:47 ` [PATCH v2 5/5] MyFirstContribution: drop PR description for GGG single-patch contributions Philippe Blain via GitGitGadget 2022-05-11 10:11 ` [PATCH v2 0/5] Improve MyFirstContribution's GitGitGadget section Junio C Hamano 2022-05-11 17:45 ` Victoria Dye 2022-05-12 23:43 ` [PATCH v3 " Philippe Blain via GitGitGadget 2022-05-12 23:43 ` [PATCH v3 1/5] MyFirstContribution: add "Anatomy of a Patch Series" section Philippe Blain via GitGitGadget 2022-05-12 23:43 ` [PATCH v3 2/5] MyFirstContribution: add standalone section on cover letter Philippe Blain via GitGitGadget 2022-05-12 23:43 ` [PATCH v3 3/5] MyFirstContribution: reference "The cover letter" in "Preparing Email" Philippe Blain via GitGitGadget 2022-05-12 23:43 ` [PATCH v3 4/5] MyFirstContribution: reference "The cover letter" in GitGitGadget section Philippe Blain via GitGitGadget 2022-05-12 23:43 ` [PATCH v3 5/5] MyFirstContribution: drop PR description for GGG single-patch contributions Philippe Blain via GitGitGadget 2022-05-19 21:49 ` [PATCH v3 0/5] Improve MyFirstContribution's GitGitGadget section Junio C Hamano 2022-05-21 16:17 ` Philippe Blain 2022-05-22 1:35 ` Junio C Hamano 2022-05-24 12:29 ` Philippe Blain 2022-05-24 19:06 ` Junio C Hamano
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bc0e05b4-f185-5aa2-ee3a-cb7278fa6ab9@gmail.com \ --to=levraiphilippeblain@gmail.com \ --cc=Johannes.Schindelin@gmx.de \ --cc=emilyshaffer@google.com \ --cc=git@vger.kernel.org \ --cc=gitgitgadget@gmail.com \ --cc=philipoakley@iee.email \ --cc=sunshine@sunshineco.com \ --cc=vdye@github.com \ --subject='Re: [PATCH v2 1/5] MyFirstContribution: add "Anatomy of a Patch Series" section' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).