From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org
Subject: Let's have chalk talks, was Re: Missing notes from the Git Contributors' Summit 2021, virtual, Oct 19/20
Date: Fri, 22 Oct 2021 11:26:17 +0200 (CEST) [thread overview]
Message-ID: <1MQe5k-1mIUTU15Lq-00NjOF@mail.gmx.net> (raw)
Team,
If I did not have the impression that this was an important topic, I would
definitely stop trying to send the notes on this session.
On Fri, 22 Oct 2021, Johannes Schindelin wrote:
> The[n] brian m. carlson offered the idea to be considerate of
> reservations by participants, but also accommodate Git contributors who
> would have loved to see the presentation but were unable to attend due
> to timezones, time conflicts, etc: offer it for viewing only for a short
> while.
CB then said that it would be nice to see the other contributors face to
face, and that they really liked the idea. But they still hoped that this
new talk series would not replace the other things we do.
Another point was raised by Emily: in their internal meetings, they often
talk about patch series that are in progress, or not even started. In
other words, the discussions are somewhat ephemeral and therefore it would
not make sense to keep records of it forever.
to be continued
reply other threads:[~2021-10-22 9:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1MQe5k-1mIUTU15Lq-00NjOF@mail.gmx.net \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).