git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>,
	<git@vger.kernel.org>,  <git-packagers@googlegroups.com>
Subject: Re: [ANNOUNCE] Git v2.48.1 and friends
Date: Tue, 14 Jan 2025 17:28:12 -0800	[thread overview]
Message-ID: <xmqqo70827df.fsf@gitster.g> (raw)
In-Reply-To: <045701db66da$36a358a0$a3ea09e0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Tue, 14 Jan 2025 18:15:28 -0500")

<rsbecker@nexbridge.com> writes:

> I will not be able to package this. The reason is that only official commits
> are
> permitted in the highly regulated customer base that I have to support.

Well, you probably want to be a bit more careful.

Think what *exactly* is *this* in "package this" in your message,
for example.

Will it be the resulting checkout of "git clone --single" of that
tag?  Then you can go there and say "make", and as Dscho explained,
what Dscho wrote in DEF_VER does not matter.  The tag that points at
that checked out commit is v2.47.2 and that is what resulting "git
version" would say.

Will it be the tarball extract from the git-2.47.2.tar.gz that is
available at https://www.kernel.org/pub/software/scm/git/?  Then you
can go there and say "make", and what Dscho wrote in DEF_VER does
not matter, either, because the official tarball contains the
'version' file that says "2.47.2" and that is the version used by
the resulting "git version".


  reply	other threads:[~2025-01-15  1:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:00 [ANNOUNCE] Git v2.48.1 and friends Junio C Hamano
2025-01-14 18:44 ` Johannes Schindelin
2025-01-14 19:08   ` rsbecker
2025-01-14 21:05     ` Johannes Schindelin
2025-01-14 23:15       ` rsbecker
2025-01-15  1:28         ` Junio C Hamano [this message]
2025-01-15  2:05           ` rsbecker
2025-01-15  5:27             ` Junio C Hamano
2025-01-14 21:11   ` Junio C Hamano

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=xmqqo70827df.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=rsbecker@nexbridge.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).