From: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
To: Derrick Stolee <derrickstolee@github.com>
Cc: Luna Jernberg <droidbittin@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>
Subject: Re: [Outreachy] internship contribution
Date: Tue, 11 Oct 2022 09:48:28 +0300 [thread overview]
Message-ID: <CA+PPyiFC0mjvY494AVZMB952Ux-TPyA-Uetu1xQ6FiHA_vaRaA@mail.gmail.com> (raw)
In-Reply-To: <ae8a98d9-eec1-cdcd-67a3-695aaca7f5ae@github.com>
Simple steps that I followed on windows 10
-open the command line application with administrator rights
-run wsl --install.
- Restart the computer
-check installed distributions, wsl --list --online
-run ubuntu distribution, wsl -d ubuntu
-add username and password
After the above steps I was able to set up git on ubuntu
NB: to start wsl when you stopped, just type wsl -u "the username u
created" in the command line
On Mon, Oct 10, 2022 at 9:22 PM Derrick Stolee <derrickstolee@github.com> wrote:
>
> On 10/10/2022 2:17 PM, NSENGIYUMVA WILBERFORCE wrote:
> > thank you all for your suggestions, let me see what is easy for me
> >
> > On Mon, Oct 10, 2022 at 7:58 PM Luna Jernberg <droidbittin@gmail.com> wrote:
> >>
> >> Maybe WSL can be used?: https://learn.microsoft.com/en-us/windows/wsl/install
>
> If you do go the WSL route, then please share your learnings by updating the
> contributing doc either in git-for-windows/git [1] or here on the mailing list.
>
> [1] https://github.com/git-for-windows/git/blob/main/CONTRIBUTING.md
>
> Thanks,
> -Stolee
next prev parent reply other threads:[~2022-10-11 6:48 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
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 [this message]
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
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=CA+PPyiFC0mjvY494AVZMB952Ux-TPyA-Uetu1xQ6FiHA_vaRaA@mail.gmail.com \
--to=nsengiyumvawilberforce@gmail.com \
--cc=christian.couder@gmail.com \
--cc=derrickstolee@github.com \
--cc=droidbittin@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@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.
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).