From: Christian Couder <christian.couder@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
Hariom verma <hariom18599@gmail.com>
Subject: Re: Git in Outreachy? (December 2022)
Date: Wed, 28 Sep 2022 08:13:17 +0200 [thread overview]
Message-ID: <CAP8UFD2FsBhYEAEttmg2GQzrho3TA2UR88wV4q01FJ5y8EzndA@mail.gmail.com> (raw)
In-Reply-To: <YzN6btb9IzqeTEdi@nand.local>
On Wed, Sep 28, 2022 at 12:34 AM Taylor Blau <me@ttaylorr.com> wrote:
>
> On Mon, Sep 26, 2022 at 11:51:23AM +0200, Christian Couder wrote:
> > The deadline to submit projects is September 29, so next Thursday.
>
> FWIW, this was extended to make October 6th (at 4pm UTC) the deadline
> for submitting projects.
Yeah, they sent an email to extend it yesterday.
> > I think Taylor agreed in private discussions with submitting another
> > project related to improving our https://git-scm.com/ website (which
> > was discussed previously on the mailing list).
>
> That's not quite the case. If I recall correctly, I said that I'd be
> excited for somebody to submit that project. But I don't have the
> capacity nor the skills to mentor it this cycle. If somebody else is,
> I'd be happy to work with them to find funding for it.
Sorry for misremembering what you said.
The thread where this was publicly discussed started there:
https://lore.kernel.org/git/CAP8UFD2fN=c2JvvzH94Nu8yqt2MOOtXrn29eFxuie9aZ5YVjQw@mail.gmail.com/
prev parent reply other threads:[~2022-09-28 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 16:57 Git in Outreachy? (December 2022) Taylor Blau
2022-08-30 6:53 ` Christian Couder
2022-09-26 9:51 ` Christian Couder
2022-09-26 17:52 ` Hariom verma
2022-09-27 8:03 ` Christian Couder
2022-09-27 22:34 ` Taylor Blau
2022-09-28 6:13 ` Christian Couder [this message]
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=CAP8UFD2FsBhYEAEttmg2GQzrho3TA2UR88wV4q01FJ5y8EzndA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=me@ttaylorr.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).