git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: straw poll: git merge conference location
Date: Thu, 14 Mar 2019 09:23:35 -0700	[thread overview]
Message-ID: <CABPp-BEj3oxdhcFf-jQJbkCTOhjT2E-yMJhCpdTAbeb4xVTVAQ@mail.gmail.com> (raw)
In-Reply-To: <20190313205539.GA30425@sigill.intra.peff.net>

On Wed, Mar 13, 2019 at 1:58 PM Jeff King <peff@peff.net> wrote:
>
> I took an informal poll at the last contributor summit in Brussels, but
> that obviously has some bias. So I'll ask here: do you have a location
> preference for a Git Merge conference (and associated contributor
> summit) next March?
>
> We're looking at doing it in North America, but there are two specific
> questions:
>
>   - is there preference between East Coast vs West Coast?
>
>   - preferences between Canada and US?
>
> There's no commitment, but please only share your opinion if it might
> actually impact your decision (i.e., if you might actually attend the
> contribu summit). Feel free to email me off-list if you don't want to
> start a flamewar about countries or coasts. :)

You are probably not surprised to hear me vote in favor of North
America, but I'd like to point out that unless some responses didn't
reach my inbox, it looks like 100% of respondents so far are in favor
of doing it on this side of the pond.  ;-)

I'm fine with East or West coast, US or Canada.  Very minor preference
for west coast, but whatever works for the most people is best.  I'll
even try to go to Europe again if that's what works for most people,
but I might not make it if it's there.

  reply	other threads:[~2019-03-14 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 20:55 straw poll: git merge conference location Jeff King
2019-03-14 16:23 ` Elijah Newren [this message]
2019-03-14 16:41   ` Johannes Schindelin
2019-03-14 17:00 ` Derrick Stolee
2019-03-14 18:26 ` Konstantin Ryabitsev
2019-03-14 18:40   ` Robert P. J. Day
2019-03-14 20:31 ` Ævar Arnfjörð Bjarmason
2019-03-15  3:38   ` Jeff King
2019-03-15 15:12     ` Johannes Schindelin

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=CABPp-BEj3oxdhcFf-jQJbkCTOhjT2E-yMJhCpdTAbeb4xVTVAQ@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).