git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: "Michal Suchánek" <msuchanek@suse.de>,
	"Alice Merrick" <amerrick@google.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: Let's have a user experience workshop
Date: Wed, 16 Mar 2022 15:05:12 -0700	[thread overview]
Message-ID: <xmqqk0ctk0yv.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZnKebM4m3AXW6+RBY7dBsQhAcReqd61VtXHNjcnPBeemQ@mail.gmail.com> (Emily Shaffer's message of "Wed, 16 Mar 2022 13:41:59 -0700")

Emily Shaffer <emilyshaffer@google.com> writes:

> Git already uses Google Groups for the security list (e.g. for fixing
> pre-disclosure security issues) and for the mentoring list, and it's
> fine to subscribe to one with a non-Google account; it acts just as a
> normal mailing list in your inbox.

I think the groups.google URL is not the one that acts just as a
normal mailing list.  <git-ux@googlegroups.com> address may be what
needs to be advertised.

I would prefer to see such a discussion on this list, too, not on a
separate place people need to subscribe to, though.

Thanks.

  parent reply	other threads:[~2022-03-16 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 21:04 Alice Merrick
2022-03-16 17:36 ` Philip Oakley
2022-03-16 17:48   ` Emily Shaffer
2022-03-16 21:50     ` Philip Oakley
2022-03-16 20:10 ` Michal Suchánek
2022-03-16 20:41   ` Emily Shaffer
2022-03-16 21:34     ` Michal Suchánek
2022-03-16 22:05     ` Junio C Hamano [this message]
2022-05-10  3:35 ` Jonathan Nieder
2022-05-12 22:23   ` Emily Shaffer
2022-05-15 16:17     ` Jonathan Nieder
2022-05-16  7:43       ` Emily Shaffer
2022-05-20 16:17         ` Alice Merrick
2022-05-20 16:22           ` rsbecker

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=xmqqk0ctk0yv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=amerrick@google.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --subject='Re: Let'\''s have a user experience workshop' \
    /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

Code repositories for project(s) associated with this 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).