Git development
 help / color / mirror / Atom feed
From: "Samo Pogačnik" <samo_pogacnik@t-2.net>
To: "René Scharfe" <l.s.r@web.de>,
	"Owen Stephens" <owen@owenstephens.co.uk>,
	git@vger.kernel.org
Subject: Re: [Bug] fetch --deepen truncates history in v2.54.0
Date: Tue, 05 May 2026 23:26:39 +0200	[thread overview]
Message-ID: <b8cbdc24c871d96c85da590853a036263b90f92f.camel@t-2.net> (raw)
In-Reply-To: <e8257951-4ea7-40ba-8043-f4f2a080b70b@web.de>

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

On Tue, 2026-05-05 at 22:34 +0200, René Scharfe wrote:
> On 5/5/26 9:27 PM, Samo Pogačnik wrote:
> > 
> > Hi, thanks for pointing out this edge case. Would you care to check the
> > following change (the provided test is also a bit modified):
> 
> There's spurious wrapping in the patch, but the changes look good to me.
> 
> Care to send them with a commit message and sign-off?
> 
I will, but it may take a while.

thanks, Samo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-05-05 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 11:27 [Bug] fetch --deepen truncates history in v2.54.0 Owen Stephens
2026-04-29 13:14 ` Owen Stephens
2026-04-29 13:16 ` D. Ben Knoble
2026-04-30  9:10   ` Mikael Magnusson
2026-05-02  9:22 ` René Scharfe
2026-05-02 20:26   ` René Scharfe
2026-05-05 19:27     ` Samo Pogačnik
2026-05-05 20:34       ` René Scharfe
2026-05-05 21:26         ` Samo Pogačnik [this message]
2026-05-06 21:56         ` [PATCH 1/1] shallow: fix relative deepen on non-shallow repositories Samo Pogačnik
2026-05-11  0:09           ` Junio C Hamano
2026-05-11  7:45             ` René Scharfe
2026-05-11  8:30               ` Junio C Hamano
2026-05-11 19:20                 ` [PATCH v2] " Samo Pogačnik

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=b8cbdc24c871d96c85da590853a036263b90f92f.camel@t-2.net \
    --to=samo_pogacnik@t-2.net \
    --cc=git@vger.kernel.org \
    --cc=l.s.r@web.de \
    --cc=owen@owenstephens.co.uk \
    /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