From: Junio C Hamano <gitster@pobox.com>
To: Josh Steadmon <steadmon@google.com>
Cc: git@vger.kernel.org, git-packagers@googlegroups.com,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: Problems publishing Rust crates
Date: Fri, 14 Mar 2025 13:46:25 -0700 [thread overview]
Message-ID: <xmqq34fffihq.fsf@gitster.g> (raw)
In-Reply-To: <4zi3re4viluih7qwvwlu7mp3j6e6gjexz2bppa5am45nnqkezz@7vtwmyrfdwvi> (Josh Steadmon's message of "Fri, 14 Mar 2025 12:43:32 -0700")
Josh Steadmon <steadmon@google.com> writes:
> To prevent squatters from stealing the libgit* crate names, I've
> published placeholder crates, which we can replace once we've fixed the
> build issues.
Thanks for being proactive. Very much appreciated.
next prev parent reply other threads:[~2025-03-14 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 17:16 [ANNOUNCE] Git v2.49.0 Junio C Hamano
2025-03-14 19:43 ` Problems publishing Rust crates (was: [ANNOUNCE] Git v2.49.0) Josh Steadmon
2025-03-14 20:12 ` brian m. carlson
2025-03-14 20:46 ` Junio C Hamano [this message]
2025-03-17 18:49 ` Josh Steadmon
2025-03-15 20:21 ` [ANNOUNCE] Git v2.49.0 rsbecker
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=xmqq34fffihq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=steadmon@google.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).