Git development
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Kristofer Karlsson <krka@spotify.com>,
	Patrick Steinhardt <ps@pks.im>,
	git@vger.kernel.org
Subject: Re: [PATCH] describe: count the distance correctly when commit dates are skewed
Date: Wed, 11 Nov 2026 13:07:47 +0100	[thread overview]
Message-ID: <avRakxssSCm1qQ4B@ugly.lan> (raw)
In-Reply-To: <CAHk-=wj-5hp+FZBAqryzTwJ8DKvuNHub2e0kUG3g_+7borFfEQ@mail.gmail.com>

On Wed, Nov 04, 2026 at 10:29:27AM -0800, Linus Torvalds wrote:
>For the kernel, people figured out what the issue is: it's not clock
>skew, it's intentional bad behavior by the gitlab Marge-bot merge
>logic.
>[...]
>Don't ask me what complete insanity caused somebody to think that
>keeping the committer name and email should mean that you should also
>lie about the commit *date*.
>
dude! you forgot the "content warning: asbestos underwear required" 
disclaimer ... ;-)

anyway, i suspect that nobody actually thought about this at all, and 
it's simply a result of the default view of committer/-date (and 
author/-date) as pseudo-atomic entities. of course, closer consideration 
reveals this to be a not necessarily helpful view, see also [1].

[1] https://lore.kernel.org/all/CAP9es6tyaGwfTguz5zgBmE5xN7MLDN3-rxRfo_JJBf79RCNzgg@mail.gmail.com/T/#u

  reply	other threads:[~2026-11-11 12:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31  6:55 [PATCH] describe: count the distance correctly when commit dates are skewed Linus Torvalds
2026-10-31 12:31 ` Tuomas Ahola
2026-11-01  1:07   ` Junio C Hamano
2026-11-01  9:46     ` Tuomas Ahola
2026-11-01 18:12       ` Junio C Hamano
2026-11-02  6:17     ` SZEDER Gábor
2026-11-02 12:46 ` Patrick Steinhardt
2026-11-02 14:20   ` Derrick Stolee
2026-11-02 17:03     ` Junio C Hamano
2026-11-02 17:52       ` Derrick Stolee
2026-11-02 18:37   ` Linus Torvalds
2026-11-03  7:16     ` Patrick Steinhardt
2026-11-03 15:58       ` Linus Torvalds
2026-11-04  0:34       ` Junio C Hamano
2026-11-04 11:01         ` Kristofer Karlsson
2026-11-04 18:17           ` Junio C Hamano
2026-11-04 18:29             ` Linus Torvalds
2026-11-11 12:07               ` Oswald Buddenhagen [this message]
2026-11-05 15:42             ` Kristofer Karlsson
2026-11-05 17:28               ` 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=avRakxssSCm1qQ4B@ugly.lan \
    --to=oswald.buddenhagen@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=krka@spotify.com \
    --cc=ps@pks.im \
    --cc=torvalds@linux-foundation.org \
    /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