Git development
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git Merge 2025 Schedule and Contributor's Summit Registration
Date: Fri, 13 Jun 2025 18:11:58 -0400	[thread overview]
Message-ID: <aEyiLhDjSzQhpJnK@nand.local> (raw)

Hi everybody,

I'm excited to share that the set of accepted talks for Git Merge 2025
are now available at:

  https://git-merge.com

Thanks to everybody who submitted a proposal. We received a lot of great
submissions, and would have accepted many more if we had the time to fit
them in.

In addition to the speakers, and schedule of talks, registration for the
Contributor's Summit is also live. As before, the main details from the
original announcement[1] are:

   When: September 29th and 30th
  Where: GitHub HQ, 88 Colin P Kelly Jr. St., San Francisco, CA 94107
   What: Main conference on the 29th, breakouts and Contributor's Summit
         on the 30th.

If you have any questions, please feel free to respond here, or
off-list. I'm looking forward to seeing folks either in person in San
Francisco, or virtually soon ;-).

Thanks,
Taylor

[1]: https://lore.kernel.org/git/Z+L3Mt58n18KUNzs@nand.local/

                 reply	other threads:[~2025-06-13 22:12 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=aEyiLhDjSzQhpJnK@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