git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>, Eric Wong <e@80x24.org>,
	Kerry@google.com, Richard <richard.kerry@atos.net>
Subject: Re: [PATCH v3] MyFirstContribution: add avenues for getting help
Date: Thu, 12 Dec 2019 20:14:29 -0800	[thread overview]
Message-ID: <20191213041429.GC135450@google.com> (raw)
In-Reply-To: <f3037862-b8f7-d674-4b1e-7b9df3fa49cd@gmail.com>

On Thu, Dec 12, 2019 at 10:00:45PM -0500, Derrick Stolee wrote:
> On 12/12/2019 8:31 PM, Emily Shaffer wrote:
> > With https://public-inbox.org/git/20191114194708.GD60198@google.com/ we
> 
> We are trying to move to lore.kernel.org, I think.

Argh, and I even wordsmithed a few paragraphs down in this commit
message too. Sending..

> 
> > now have a mentoring mailing list, to which we should direct new
> > contributors who have questions.
> > 
> > Since #git-devel's traffic is fairly low, it should be OK to direct some
> > questions there too. Mention some of the conventions in case folks are
> > unfamiliar with IRC.
> > 
> > Because the mentoring list and #git-devel are both a subset of Git
> > contributors, finally list the main Git list and mention some of the
> > posting conventions.
> > 
> > Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
> > ---
> > Since v2:
> > 
> > - Removed a double slash in a URL
> > - public-inbox -> lore.kernel.org
> 
> Ah, I see you mentioned it here and in the contents. Commit messages
> are harder to keep straight, in my experience.
> 
> > +==== https://lore.kernel.org/git[git@vger.kernel.org]

  reply	other threads:[~2019-12-13  4:14 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 21:53 [PATCH] MyFirstContribution: add avenues for getting help Emily Shaffer
2019-11-15 22:05 ` Denton Liu
2019-11-15 23:03   ` Emily Shaffer
2019-11-15 23:06 ` [PATCH v2] " Emily Shaffer
2019-11-15 23:38   ` Johannes Schindelin
2019-11-16  0:09   ` Jonathan Nieder
2019-11-16  3:05   ` Junio C Hamano
2019-11-18 21:45     ` Emily Shaffer
2019-11-19  1:45       ` Junio C Hamano
2019-11-19 18:49       ` SZEDER Gábor
2019-11-19 21:29         ` Johannes Schindelin
2019-11-19 21:41           ` SZEDER Gábor
2019-11-20  1:50             ` Eric Wong
2019-11-20 11:41             ` Johannes Schindelin
2019-11-20 23:40               ` SZEDER Gábor
2019-11-20 10:45           ` Kerry, Richard
2019-11-20 11:37             ` Junio C Hamano
2019-11-19 18:25   ` SZEDER Gábor
2019-12-13  1:31   ` [PATCH v3] " Emily Shaffer
2019-12-13  3:00     ` Derrick Stolee
2019-12-13  4:14       ` Emily Shaffer [this message]
2019-12-13  4:16       ` [PATCH v4] " Emily Shaffer
2019-12-13 17:20     ` [PATCH v3] " Junio C Hamano
2019-12-13 17:49       ` Emily Shaffer
2019-12-13 18:40         ` Junio C Hamano
2020-01-24 20:09     ` [PATCH v5] " emilyshaffer
2020-01-24 20:35       ` Junio C Hamano
2020-01-24 20:50         ` Emily Shaffer
2020-01-24 20:54           ` Emily Shaffer
2020-01-24 21:11           ` Junio C Hamano
2020-01-24 21:01       ` [PATCH v6] " Emily Shaffer
2020-01-24 21:18         ` Junio C Hamano
2020-01-24 21:20           ` Emily Shaffer
2020-01-24 21:26         ` [PATCH v7] " Emily Shaffer
2020-01-24 21:56           ` SZEDER Gábor
2020-01-24 23:44             ` Junio C Hamano
2020-02-06  1:07               ` SZEDER Gábor
2020-02-06 16:33                 ` Junio C Hamano
2020-02-06 19:49                   ` Emily Shaffer
2020-02-06 22:13                     ` Emily Shaffer
2020-02-14  2:03                   ` [PATCH] MyFirstContribution: rephrase contact info Emily Shaffer
2020-02-14  2:10                     ` Jonathan Nieder
2020-02-14 17:36                       ` Junio C Hamano
2020-01-24 22:05           ` [PATCH v7] MyFirstContribution: add avenues for getting help Junio C Hamano

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=20191213041429.GC135450@google.com \
    --to=emilyshaffer@google.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Kerry@google.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=liu.denton@gmail.com \
    --cc=richard.kerry@atos.net \
    --cc=stolee@gmail.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).