From: Taylor Blau <me@ttaylorr.com>
To: Aditya Sirish A Yelgundhalli <aditya.sirish@nyu.edu>
Cc: git@vger.kernel.org, Scott Chacon <schacon@gmail.com>
Subject: Re: [ANNOUNCE] Git Merge 2024, September 19-20, 2024, Berlin
Date: Tue, 21 May 2024 18:23:07 -0400 [thread overview]
Message-ID: <Zk0ey1848sjGlBXj@nand.local> (raw)
In-Reply-To: <835eb66a-737b-40e5-99be-af299e231408@nyu.edu>
On Tue, May 21, 2024 at 07:47:35AM +0530, Aditya Sirish A Yelgundhalli wrote:
> Hello!
>
> This is very exciting! Could you share when the CFP is likely to close?
> Also, is there at all the possibility of having a co-speaker?
I don't think we're likely to close the CFP anytime soon, but I'm sure
that we'll give the list a healthy "heads up" before doing so.
I don't personally have any issues with having a co-speaker; I assume
the same is true of Scott.
Thanks,
Taylor
next prev parent reply other threads:[~2024-05-21 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 17:37 [ANNOUNCE] Git Merge 2024, September 19-20, 2024, Berlin Taylor Blau
2024-05-21 2:17 ` Aditya Sirish A Yelgundhalli
2024-05-21 22:23 ` Taylor Blau [this message]
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=Zk0ey1848sjGlBXj@nand.local \
--to=me@ttaylorr.com \
--cc=aditya.sirish@nyu.edu \
--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 NNTP newsgroup(s).