Skip to content

Commit 4d6cd56

Browse files
committed
Mention that GGG can also be used on github.com/git/git
1 parent 05d23d6 commit 4d6cd56

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

index.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@
4545
Apart from lacking the convenience of a web interface, this process also puts considerable demands on the code contributions: the mails are expected to be plain text only (no HTML!), for example, and the diffs embedded in the mails must apply cleanly (no whitespace changes!), among other things.
4646
</p><p>
4747
A few tutorials out there try to help with this process (e.g. <a href="https://github.com/git-for-windows/git/blob/master/CONTRIBUTING.md">Git for Windows' detailed instructions how to contribute patches to the Git project</a>, or Git's <a href="https://git-scm.com/docs/MyFirstContribution">MyFirstContribution tutorial</a>).
48-
GitGitGadget tries a different approach: allow contributing patches to the Git project itself by opening a Pull Request at <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> and let GitGitGadget prepare and send the corresponding mails.
48+
GitGitGadget tries a different approach: allow contributing patches to the Git project itself by opening a Pull Request either at <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> or directly at <a href="https://github.com/gitgitgadget/git">https://github.com/git/git</a> and let GitGitGadget prepare and send the corresponding mails.
4949
</p>
5050
</div>
5151

@@ -54,7 +54,7 @@ <h2>How can you use GitGitGadget?</h2>
5454
<p>
5555
So you cloned <a href="https://github.com/git/git">https://github.com/git/git</a> and implemented a bug fix or a new feature?
5656
And you already pushed it to your own fork?
57-
Good, now is the time to direct your web browser to <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> and to open a Pull Request.
57+
Good, now is the time to direct your web browser to <a href="https://github.com/gitgitgadget/git">https://github.com/gitgitgadget/git</a> (or to <a href="https://github.com/gitgitgadget/git">https://github.com/git/git</a> ) and to open a Pull Request.
5858
Please make sure to use a descriptive Pull Request title and description; GitGitGadget will use these as the cover letter.
5959
You will also want to read <a href="https://git-scm.com/docs/SubmittingPatches">Git's guidelines</a> to make sure that your contributions are in the expected form.
6060
</p><p>

0 commit comments

Comments
 (0)