Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: [POLL] Git Merge 2023 dates
Date: Fri, 28 Apr 2023 22:39:44 -0400	[thread overview]
Message-ID: <ZEyDcBcGmLznqKzD@nand.local> (raw)

GitHub is beginning to look at Git Merge dates for 2023. There are a
couple of options being considered, and I'm curious which one would be
preferable to folks.

We are considering either of:

  - The third week of September in Bilbao, Spain, or
  - Mid-October in Raleigh, North Carolina, USA

These dates are centered around Open Source Summit Europe and All Things
Open, respectively [1, 2]. We're thinking that Git Merge would occur
either shortly before or after those conferences, for folks that want to
go to both / maximize their travel / etc.

Let me know which of the above you would be able to attend (ideally
off-list, to avoid this thread becoming too noisy).

Thanks,
Taylor

[1]: https://2023.allthingsopen.org/
[2]: https://events.linuxfoundation.org/open-source-summit-europe/

             reply	other threads:[~2023-04-29  2:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29  2:39 Taylor Blau [this message]
2023-05-16  7:20 ` [POLL] Git Merge 2023 dates Toon Claes

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=ZEyDcBcGmLznqKzD@nand.local \
    --to=me@ttaylorr.com \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).