Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Toon Claes <toon@iotcl.com>
To: me@ttaylorr.com
Cc: git@vger.kernel.org, Toon Claes <toon@iotcl.com>
Subject: Re: [POLL] Git Merge 2023 dates
Date: Tue, 16 May 2023 09:20:07 +0200	[thread overview]
Message-ID: <20230516072007.338103-1-toon@iotcl.com> (raw)
In-Reply-To: <ZEyDcBcGmLznqKzD@nand.local>

Hi Taylor,

I quickly wanted to share my personal preference regarding Git Merge
2023.

>  - The third week of September in Bilbao, Spain, or

I would love to see Git Merge happen in Europe this yeas. But I was
looking at the Open Source Summit Europe schedule and it's a bit
unfortunate the conf is from Tuesday till Thursday. Usually we have two
days for Git Merge, so are you planning to have one day before and one
day after that conf? Anyhow, personally I'm stuck from the 22th
September. So I'd prefer Git Merge to happen before OSSE.

>  - Mid-October in Raleigh, North Carolina, USA

On my agenda this would fit in better, although it's harder for me to
get there.

I'm not sure this provides you a lot of constructive feedback, but I
wanted to let you know anyway.

One other note, are you planning a full day for the Contributor Summit
again? Because I felt the half day last time was too short.

Also if GitHub is interested in any help/support from GitLab to set up
Git Merge, I'm happy to hook you up with the correct people.

--
Toon

      reply	other threads:[~2023-05-16  7:20 UTC|newest]

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

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=20230516072007.338103-1-toon@iotcl.com \
    --to=toon@iotcl.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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.
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).