From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Scott Chacon <schacon@gmail.com>
Subject: [ANNOUNCE] Git Merge 2024, September 19-20, 2024, Berlin
Date: Thu, 9 May 2024 13:37:12 -0400 [thread overview]
Message-ID: <Zj0JyL1b+g1G3zWx@nand.local> (raw)
Git Merge 2024 is happening in-person on September 19th and 20th in
Berlin!
GitButler and GitHub are co-hosting the event, which will take place
over two days in Berlin and allow developers and community members to
get together and talk about the future of Git.
Here are the details for the main conference:
When: September 19th and 20th
Where: Location TBD (in Berlin, Germany)
What: Talks on the 19th, birds of a feather discussions on the 20th.
This email is just to announce the date so people can start planning for
the main conference and BOF discussions.
Registration for the event is still being set up, but it should
hopefully be live in the next short while. I'll reply to this email when
I have some more details.
In the meantime, the CFP site is up and running. If you have any
interest in giving a talk, please consider submitting a proposal here:
https://bit.ly/git-merge-2024-cfp
If you'd like to come but need financial assistance with travel costs,
please reach out to the Git PLC at <git@sfconservancy.org>. We'll
collect requests and try to make decisions and notify people by
mid-August, which would hopefully still leave time for making travel
arrangements.
Other than that, please be thinking about (and feel free to discuss in
this thread) topics you'd like to discuss, or any general thoughts on
the format, venue setup, etc.
Thanks,
Scott Chacon (GitButler)
Taylor Blau (GitHub)
next reply other threads:[~2024-05-09 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 17:37 Taylor Blau [this message]
2024-05-21 2:17 ` [ANNOUNCE] Git Merge 2024, September 19-20, 2024, Berlin Aditya Sirish A Yelgundhalli
2024-05-21 22:23 ` Taylor Blau
2024-07-05 14:12 ` Aditya Sirish A Yelgundhalli
2024-07-05 21:01 ` Taylor Blau
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=Zj0JyL1b+g1G3zWx@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=schacon@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.
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).