From: Christian Couder <christian.couder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>
Subject: Re: Git in Outreachy Dec-Mar?
Date: Sat, 8 Sep 2018 10:57:46 +0200 [thread overview]
Message-ID: <CAP8UFD3y=p_w5scnB0dggqK7jb5x-2x=d4LUCXLVVGkRcAOcJg@mail.gmail.com> (raw)
In-Reply-To: <20180906193130.GA28588@sigill.intra.peff.net>
On Thu, Sep 6, 2018 at 9:31 PM, Jeff King <peff@peff.net> wrote:
> On Thu, Sep 06, 2018 at 11:51:49AM +0200, Christian Couder wrote:
>
>> Yeah, I think the https://git.github.io/Outreachy-17/ is not actually necessary.
>
> I think it still may be helpful for explaining in further detail things
> like #leftoverbits (though I see you put some of that in your project
> description).
You mean in https://git.github.io/Outreachy-17/ or somewhere else?
It is already described in https://git.github.io/SoC-2018-Microprojects/.
>> I did that for the "Improve `git bisect`" project. As the
>> "coordinator", you will need to approve that project.
>
> Thanks. I approved it, though a few of the descriptions are a little
> funny. For instance, the text says "we use an issue tracker", which then
> links to public-inbox. I assume this is because you filled in a field
> for "issue tracker" and then the system generated the text.
Yeah, it was generated from fields that I filled in.
> I don't know if there's a way go into more detail there.
I don't think so, though we could perhaps improve our web pages.
next prev parent reply other threads:[~2018-09-08 8:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 15:14 Git in Outreachy Dec-Mar? Jeff King
2018-08-29 13:12 ` Ævar Arnfjörð Bjarmason
2018-08-30 3:16 ` Jeff King
2018-08-30 11:46 ` Johannes Schindelin
2018-08-30 19:24 ` Jeff King
2018-08-31 8:54 ` Christian Couder
2018-08-31 10:30 ` Оля Тележная
2018-09-01 7:11 ` Christian Couder
2018-09-01 8:34 ` Jeff King
2018-08-30 12:18 ` Ævar Arnfjörð Bjarmason
2018-08-30 19:42 ` Jeff King
2018-09-05 13:23 ` Ævar Arnfjörð Bjarmason
2018-08-31 8:16 ` Christian Couder
2018-09-01 8:43 ` Jeff King
2018-09-02 7:37 ` Christian Couder
2018-09-02 8:43 ` Jeff King
2018-09-03 4:36 ` Christian Couder
2018-09-05 7:20 ` Christian Couder
2018-09-06 1:14 ` Jeff King
2018-09-06 9:58 ` Christian Couder
2018-09-06 19:34 ` Jeff King
2018-09-08 8:59 ` Christian Couder
2018-09-06 1:21 ` Jeff King
2018-09-06 9:51 ` Christian Couder
2018-09-06 19:31 ` Jeff King
2018-09-08 8:57 ` Christian Couder [this message]
2018-09-08 15:40 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3y=p_w5scnB0dggqK7jb5x-2x=d4LUCXLVVGkRcAOcJg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).