Re: [GSOC] Introduction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christian,

On Thu, Jan 23, 2020 at 4:46 PM Christian Couder
<christian.couder@xxxxxxxxx> wrote:
>
> It is not clear looking only at the links if the issues you solved
> have resulted in some patches posted to the Git mailing list or just
> fixes in Git for Windows. Could you give us more details about that?
> For example if you sent emails to the mailing list could you send
> links to those emails?

My apologies, here are the links to the patches[1][2].

> If you have already sent patches to the mailing list and they have
> been accepted, you don't need to work on a microproject.

Both have been accepted and merged successfully. Those are just minor
issues, so I don't they can be qualify as microproject. Although I
forgot to tag [GSoC] with the patches.

Few Doubts:
1. Do I need to tag [GSoC] with every patch I will send before GSoC or
just only with a microproject?
2. Can I use GitGitGadget throughout the GSoC period and for my
microproject? (I'm quite liking this tool)

Regards,
Hariom

[1]: https://public-inbox.org/git/3b4b8e0353d705ea649c9fb608c021b35e6d8f5b.1571250635.git.gitgitgadget@xxxxxxxxx/
[2]: https://public-inbox.org/git/177deddcf83c2550c0db536a7a6942ba69a92fa5.1574600963.git.gitgitgadget@xxxxxxxxx/



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux