Re: Fetching upstream remote fails if repo was a blobless clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jeff King <peff@xxxxxxxx>
Subject: Re: Fetching upstream remote fails if repo was a blobless clone
From: Justin Su <injustsu@xxxxxxxxx>
Date: Sat, 2 Aug 2025 14:02:57 -0400
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <20250802093226.GF3711639@coredump.intra.peff.net>
References: <CAB=S_8+LMsSpnRWQZwK2Dj63WdcPy1vp+aJ=erDbf_aaPoU3cA@mail.gmail.com> <20250802093226.GF3711639@coredump.intra.peff.net>

On Sat, Aug 2, 2025 at 5:32 AM Jeff King <peff@xxxxxxxx> wrote:

> Is it still happening for you?

Yes, I can still reproduce with that sequence of commands.

Follow-Ups:
- Re: Fetching upstream remote fails if repo was a blobless clone
  - From: Justin Su

References:
- Fetching upstream remote fails if repo was a blobless clone
  - From: Justin Su
- Re: Fetching upstream remote fails if repo was a blobless clone
  - From: Jeff King

Prev by Date: Re: Why does git-grep appear to treat exclude pathspecs differently?
Next by Date: Re: Fetching upstream remote fails if repo was a blobless clone
Previous by thread: Re: Fetching upstream remote fails if repo was a blobless clone
Next by thread: Re: Fetching upstream remote fails if repo was a blobless clone
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux