git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: [ANNOUNCE] Additional travel sponsorships for Git Merge 2025
Date: Thu, 3 Jul 2025 17:25:08 -0400	[thread overview]
Message-ID: <aGb1NAHN/+T/3oYH@nand.local> (raw)

This is a small follow-up to the Git Merge[1] announcement to say that
we are **accepting more requests for travel sponsorships** to attend
the conference.

Some details:

 - This is open to not only previous GSoC and Outreachy contributors,
   but to current GSoC contributors as well.

 - If you are in either of these groups and interested in applying,
   please email <git@sfconservancy.org> anytime before July 15, 2025
   for more details.

I'm looking forward to seeing many of you either in person or
virtually in September. If you have any other questions in the
meantime, please feel free to reach out to me either on- or off-list
directly.

Thanks,
Taylor

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

                 reply	other threads:[~2025-07-03 21:25 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=aGb1NAHN/+T/3oYH@nand.local \
    --to=me@ttaylorr.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 NNTP newsgroup(s).