From: Derrick Stolee <derrickstolee@github.com>
To: Christian Couder <christian.couder@gmail.com>,
NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>
Subject: Re: [Outreachy] internship contribution
Date: Mon, 10 Oct 2022 12:33:26 -0400 [thread overview]
Message-ID: <9fcfc8b0-772d-08c3-595b-5a5a139d7ecd@github.com> (raw)
In-Reply-To: <CAP8UFD26PY-53vZNZJzCRNiqaVB4fd=AvBtVuvMQP9p8Oqj82Q@mail.gmail.com>
On 10/10/2022 12:22 PM, Christian Couder wrote:
> On Mon, Oct 10, 2022 at 2:19 PM NSENGIYUMVA WILBERFORCE
> <nsengiyumvawilberforce@gmail.com> wrote:
>>
>> I see most of the articles are UNIX based, does it mean that I should
>> have a UNIX based operating system in order to contribute?
>> Currently, I have windows installed 11 on my PC
>
> You can install a Linux virtual machine on your PC and develop in this
> virtual machine, or you can install the Git for Windows SDK from:
>
> https://gitforwindows.org/#contribute
>
> It might be best to install both development environments. I will not
> be able to help you much with development environment issues if you
> develop on Windows, but if it works for you, that could be Ok,
> especially if you use GitGitGadget too.
The git-for-windows/git fork has some information that is helpful
for developing Git on a Windows machine [1]. This also includes
details about recommending a Linux VM with Windows' Hyper-V system
because compiling and testing Git is so much faster on Linux.
[1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
Good luck!
-Stolee
next prev parent reply other threads:[~2022-10-10 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 4:37 [Outreachy] internship contribution NSENGIYUMVA WILBERFORCE
2022-10-10 8:19 ` Christian Couder
2022-10-10 12:18 ` NSENGIYUMVA WILBERFORCE
2022-10-10 16:22 ` Christian Couder
2022-10-10 16:33 ` Derrick Stolee [this message]
2022-10-10 16:57 ` Luna Jernberg
2022-10-10 18:17 ` NSENGIYUMVA WILBERFORCE
2022-10-10 18:22 ` Derrick Stolee
2022-10-11 6:48 ` NSENGIYUMVA WILBERFORCE
2022-10-12 3:31 ` NSENGIYUMVA WILBERFORCE
2022-10-12 4:42 ` Junio C Hamano
2022-10-12 6:45 ` Đoàn Trần Công Danh
2022-10-12 10:37 ` NSENGIYUMVA WILBERFORCE
2022-10-12 14:21 ` Christian Couder
2022-10-12 15:18 ` Đoàn Trần Công Danh
2022-10-12 16:37 ` NSENGIYUMVA WILBERFORCE
[not found] ` <CA+fEeODMVNrnFRbuNVgbBShSA2Juo8Ux5ahd2J8nCfmPetdpvA@mail.gmail.com>
2022-10-13 10:52 ` Christian Couder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fcfc8b0-772d-08c3-595b-5a5a139d7ecd@github.com \
--to=derrickstolee@github.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=nsengiyumvawilberforce@gmail.com \
/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.
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 NNTP newsgroup(s).