From: Christian Couder <christian.couder@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Jakub Narebski <jnareb@gmail.com>,
Markus Jansen <mja@jansen-preisler.de>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2020, #01; Wed, 3)
Date: Thu, 4 Jun 2020 16:39:46 +0200 [thread overview]
Message-ID: <CAP8UFD2x_j9Ne-YQes_Q9B+MAgXgM7+w2xSZpMVxNj3wnf0Rfg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD0V+=tq8CGFk_Mz+N=HjRtkhkMbX9Cy2-=WfHL8wrj6=Q@mail.gmail.com>
On Thu, Jun 4, 2020 at 4:32 PM Christian Couder
<christian.couder@gmail.com> wrote:
>
> Maybe we could just ask people to test rc releases or 'master' in Git
> Rev News? It might work better if someone wrote a small article about
> what is coming in the next release before asking to test.
Such articles and asking users to test more could also be done on
GitLab's, GitHub's, etc, corporate blogs or on Git developer's blogs
too. The content of such articles could also be shared between
different company blogs and Git Rev News to reach as many users as
possible.
next prev parent reply other threads:[~2020-06-04 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 20:59 What's cooking in git.git (Jun 2020, #01; Wed, 3) Junio C Hamano
2020-06-04 8:14 ` Elijah Newren
2020-06-04 14:32 ` Christian Couder
2020-06-04 14:39 ` Christian Couder [this message]
2020-06-06 14:53 ` Kaartic Sivaraam
2020-06-07 6:27 ` Christian Couder
2020-06-04 14:49 ` Junio C Hamano
2020-06-05 1:46 ` Elijah Newren
2020-06-06 13:57 ` Philip Oakley
2020-06-04 23:41 ` brian m. carlson
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=CAP8UFD2x_j9Ne-YQes_Q9B+MAgXgM7+w2xSZpMVxNj3wnf0Rfg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=mja@jansen-preisler.de \
--cc=newren@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).