git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Microproject on git-credential-cache
Date: Mon, 11 Feb 2019 19:00:33 -0500	[thread overview]
Message-ID: <20190212000033.GB13301@sigill.intra.peff.net> (raw)
In-Reply-To: <CAHd-oW4p6XUjF_j+XXwYWGt__L_5bTJGwxmgWhxJfpuAFac=dQ@mail.gmail.com>

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!

> 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.

> 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).

> 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. :)

-Peff

  reply	other threads:[~2019-02-12  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 23:45 [GSoC] Microproject on git-credential-cache Matheus Tavares Bernardino
2019-02-12  0:00 ` Jeff King [this message]
2019-02-12  0:23   ` Matheus Tavares Bernardino
2019-02-12  0:32     ` Jeff King
2019-02-12  0:08 ` Christian Couder
2019-02-12  0:27   ` Matheus Tavares Bernardino

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=20190212000033.GB13301@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    /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).