{"thread":{"id":"49795","subject":"Git Reference Manual enhance","startedAt":"2018-11-11T00:21:39Z","lastAt":"2018-11-12T18:39:44Z","messageCount":3,"participants":["Fredi Fowler","Eric Sunshine","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"362898","messageId":"CAEv5rCuQM_6ch3KX1ji9nY0hW9eFVomO3svg79D67PqR1uY1tg@mail.gmail.com","threadId":"49795","inReplyTo":null,"subject":"Git Reference Manual enhance","fromName":"Fredi Fowler","fromEmail":"inredikawb@gmail.com","sentAt":"2018-11-11T00:20:53Z","receivedAt":"2018-11-11T00:21:39Z","isPatch":false,"sender":{"key":"inredikawb@gmail.com","avatar":null},"body":"Is there any way to create pull request to git man (https://git-scm.com/docs)?\n\nI found there some inconsistencies. For example, almost in all pages\nare using [no-], but at https://git-scm.com/docs/git-merge each\ncommand (with [no-] or without) write separately.\n\nThere are some same inconsistencies that a easy to fix. So, if I can\nsent a pull-request for such fix – inform me.\n"},{"id":"362899","messageId":"CAPig+cTi424HcvV29NmeS3t+VV1mEmQx=pdgSpkXs5QX4HAd5w@mail.gmail.com","threadId":"49795","inReplyTo":"CAEv5rCuQM_6ch3KX1ji9nY0hW9eFVomO3svg79D67PqR1uY1tg@mail.gmail.com","subject":"Re: Git Reference Manual enhance","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2018-11-11T01:25:16Z","receivedAt":"2018-11-11T01:25:29Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Sat, Nov 10, 2018 at 7:21 PM Fredi Fowler <inredikawb@gmail.com> wrote:\n> Is there any way to create pull request to git man (https://git-scm.com/docs)?\n\nThat website is maintained as a project separate from Git, so you can\nreport issues specific to the website, or create pull requests, at its\nproject page (https://github.com/git/git-scm.com), however...\n\n> I found there some inconsistencies. For example, almost in all pages\n> are using [no-], but at https://git-scm.com/docs/git-merge each\n> command (with [no-] or without) write separately.\n>\n> There are some same inconsistencies that a easy to fix. So, if I can\n> sent a pull-request for such fix – inform me.\n\nThose manual pages are generated from documentation sources in the Git\nproject, thus those fixes should be submitted to Git itself, not to\nthe website project. Changes to Git are sent to this mailing list as\npatches (see Documentation/SubmittingPatches), although see\ngitgitgadget[1], which acts as a Github\npull-request-to-Git-mailing-list gateway, as a possible alternative.\n\n[1]: https://github.com/gitgitgadget/gitgitgadget/blob/master/README.md\n"},{"id":"363069","messageId":"20181112183939.GA44368@google.com","threadId":"49795","inReplyTo":"CAEv5rCuQM_6ch3KX1ji9nY0hW9eFVomO3svg79D67PqR1uY1tg@mail.gmail.com","subject":"Re: Git Reference Manual enhance","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-11-12T18:39:39Z","receivedAt":"2018-11-12T18:39:44Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Fredi,\n\nFredi Fowler wrote:\n\n> Is there any way to create pull request to git man (https://git-scm.com/docs)?\n>\n> I found there some inconsistencies. For example, almost in all pages\n> are using [no-], but at https://git-scm.com/docs/git-merge each\n> command (with [no-] or without) write separately.\n>\n> There are some same inconsistencies that a easy to fix. So, if I can\n> sent a pull-request for such fix – inform me.\n\nWelcome!  Yes, feel free to make improvements to the manual.  First,\nyou'll want to clone the repo:\n\n git clone https://kernel.googlesource.com/pub/scm/git/git\n\nThen make changes.  You can test using \"make\":\n\n make -C Documentation git-merge.html\n open Documentation/git-merges.html\n\nOnce you're happy with the patch, it's time to send it out for review.\nThe Git project uses a decentralized review process using email.  See\nhttps://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html\nfor details about how it works.\n\nIf you are used to the GitHub pull request process, you may enjoy\nGitGitGadget, which acts as a sort of bridge.  See [1] for\ninstructions.  Please do also keep in mind the hints from\nSubmittingPatches e.g.  about how to describe your changes and how to\ncertify your work.\n\nThanks, and looking forward to seeing your contributions,\nJonathan\n\n[1] https://github.com/gitgitgadget/gitgitgadget/blob/master/README.md#a-bot-to-serve-as-glue-between-github-pull-requests-and-the-git-mailing-list\n"}]}