Re: [GSoC] Microproject on git-credential-cache
- From
Matheus Tavares Bernardino <matheus.bernardino@usp.br>
- Date
- Feb 12, 2019, 00:23 UTC
- Message-ID
- <CAHd-oW5me9KXEgngb3GD9uhQR5FQn9GS5pBoQAfV8awkuo4iVA@mail.gmail.com>
- In-Reply-To
- <20190212000033.GB13301@sigill.intra.peff.net>
On Mon, Feb 11, 2019 at 10:00 PM Jeff King <peff@peff.net> wrote:
Show 9 quoted lines
> > On Mon, Feb 11, 2019 at 09:45:21PM -0200, Matheus Tavares Bernardino wrote: > > > I've been contributing to the Linux Kernel for the past semester and > > I'm now looking to take my first steps in the git community. I'm also > > interested in GSoC 2019. > > Hi, and welcome! >
Thanks, Jeff!
Show 10 quoted lines
> > I started looking at https://git.github.io/SoC-2019-Microprojects/ and
> > one that got my attention was "Move ~/.git-credential-cache to
> > ~/.cache/git". But looking around at the code and the mailing list,
> > this microproject seems to have been already solved at 60759ba
> > ("credential-cache: use XDG_CACHE_HOME for socket", 2017-03-17),
> > right?
>
> Yes, I think so. We should remove it from the list (you're welcome to
> submit a PR at https://github.com/git/git.github.io.
>Thanks! PR submitted :)
Show 8 quoted lines
> > For the microproject "Add configuration options for some commonly used > > command-line options", are there some options already known to be good > > for adding to configuration file? > > Hmm. I don't offhand have any suggestions. That one has been floating > around since at least 2015. I wonder if it may also be time to retire it > (or give some more concrete examples). >
So it may be better if I choose another microproject, right?
Show 10 quoted lines
> > Finally, a non GSoC-related question. Just to confirm my understanding > > of Documentation/SubmittingPatches: I must send patches to the mailing > > list first and after some feedback from community, send to the > > maintainer with CC to the list, is that correct? > > Yes. Often the maintainer will even pick them up without being cc'd (in > which case he'll usually reply to say so). The main goal is to avoid > overwhelming him with first-draft patches that are not yet ready to be > applied. :) >
Got it, thanks! I just asked because that's different from Kernel's workflow. But totally makes sense.
Matheus
> -Peff