From: Derrick Stolee <stolee@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Derrick Stolee <dstolee@microsoft.com>
Subject: [RFC] Contributing to Git (on Windows)
Date: Thu, 1 Mar 2018 12:35:39 -0500 [thread overview]
Message-ID: <176408fc-3645-66d3-2aa3-30ca3fa723e7@gmail.com> (raw)
We (Git devs at Microsoft) have had several people start contributing to
Git over the past few years (I'm the most-recent addition). As we
on-boarded to Git development on our Windows machines, we collected our
setup steps on an internal wiki page.
Now, we'd like to make that document publicly available. These steps are
focused on a Windows user, so we propose putting them in the
git-for-windows/git repo under CONTRIBUTING.md. I have a pull request
open for feedback [1]. I'll read comments on that PR or in this thread.
If you've ever done Git development on a Windows machine, I would love
to hear your feedback on this document. Any other advice you have is
greatly appreciated.
For anyone interested, there are also a discussion about submitting
patches upstream. The document links to Documentation/CodingGuidelines
and Documentation/SubmittingPatches, but tries to elaborate with
additional advice.
Thanks,
-Stolee
[1] https://github.com/git-for-windows/git/pull/1529
next reply other threads:[~2018-03-01 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 17:35 Derrick Stolee [this message]
2018-03-02 4:44 ` [RFC] Contributing to Git (on Windows) Jonathan Nieder
2018-03-02 13:38 ` Derrick Stolee
2018-03-02 16:45 ` Junio C Hamano
2018-03-03 17:34 ` Johannes Schindelin
2018-03-03 18:27 ` Jonathan Nieder
2018-03-05 14:50 ` Derrick Stolee
2018-03-05 18:13 ` Jonathan Nieder
2018-03-07 14:16 ` Johannes Schindelin
2018-03-05 16:42 ` Johannes Schindelin
2018-03-05 18:01 ` Jonathan Nieder
2018-03-05 18:26 ` Jonathan Nieder
2018-03-05 18:58 ` Eric Sunshine
2018-03-05 20:23 ` 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=176408fc-3645-66d3-2aa3-30ca3fa723e7@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).