All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Maksym Sobolyev <sobomax@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Maksym Sobolyev <sobomax@sippysoft.com>
Subject: Re: ms/customizable-ident-expansion
Date: Mon, 08 Nov 2021 20:14:23 +0100	[thread overview]
Message-ID: <211108.864k8mfocg.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CABFYoQA82u8Um6L439_bU4a+WpkdXOcbU8foPjqnVw+4MnNU0A@mail.gmail.com>


On Sun, Nov 07 2021, Maksym Sobolyev wrote:

> Junio, well it works and passes Occam Razor test. I even added a
> reasonable number of test cases. As I tried to explain at least once,
> having it per-directory might be advantageous, if the project pulls
> sources from all different places where you might "mute" ID
> replacement for certain parts of the tree or use a different one. Most
> of that would have to be thrown away if the feature is to be reworked
> to your liking.

Yes, isn't there also a practical use for this in the source trees of
the various *BSDs who import each other's sources (but I don't know if
it's useful for that).

> Totay I logged into one of our products and got this message:
>
> + sudo chroot /voicelog/src su -l sobomax
> This fortune brought to you by:
> $FreeBSD: 3325fdce090fbf738dcb1f8535d16217789cbe4e $
>
> I did not know such a fortune ever existed, it has probably been
> developed around a long-long time ago before git or even linux
> existed. Just as many other more useful features around the same idea.

This on the other hand looks both neat and a bit scary, so something
that previously left "$FreeBSD$" alone started expanding it? Hrm, I
guess since you need to set "ident" it's no big deal.

But I wonder if we'll see any downstream breakage for people who opt-in
to this, who have code they didn't know about that expects an RCS/CVS
version, and suddenly gets a SHA-1-sized hex string instead :)

  parent reply	other threads:[~2021-11-08 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30  0:17 What's cooking in git.git (Oct 2021, #07; Fri, 29) Junio C Hamano
2021-11-01 19:26 ` ab/config-based-hooks-2 (was: What's cooking in git.git (Oct 2021, #07; Fri, 29)) Ævar Arnfjörð Bjarmason
2021-11-01 20:17   ` ab/config-based-hooks-2 Junio C Hamano
2021-11-01 19:27 ` ab/only-single-progress-at-once (was: What's cooking in git.git (Oct 2021, #07; Fri, 29)) Ævar Arnfjörð Bjarmason
2021-11-01 19:30 ` tb/plug-pack-bitmap-leaks " Ævar Arnfjörð Bjarmason
2021-11-01 19:32 ` tp/send-email-completion " Ævar Arnfjörð Bjarmason
2021-11-01 19:34 ` js/scalar " Ævar Arnfjörð Bjarmason
2021-11-01 19:39 ` ms/customizable-ident-expansion " Ævar Arnfjörð Bjarmason
2021-11-01 20:23   ` ms/customizable-ident-expansion Junio C Hamano
     [not found]     ` <CABFYoQA82u8Um6L439_bU4a+WpkdXOcbU8foPjqnVw+4MnNU0A@mail.gmail.com>
2021-11-08 19:14       ` Ævar Arnfjörð Bjarmason [this message]
2021-11-08 20:01         ` ms/customizable-ident-expansion Junio C Hamano
2021-12-11  2:52 What's cooking in git.git (Dec 2021, #03; Fri, 10) Junio C Hamano
2021-12-12 22:42 ` ms/customizable-ident-expansion (was: What's cooking in git.git (Dec 2021, #03; Fri, 10)) Ævar Arnfjörð Bjarmason
2021-12-13  9:02   ` ms/customizable-ident-expansion 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=211108.864k8mfocg.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sobomax@gmail.com \
    --cc=sobomax@sippysoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.