From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: git@vger.kernel.org
Subject: Re: limiting git branch --contains
Date: Fri, 24 Mar 2023 20:58:39 +0100 [thread overview]
Message-ID: <ZB4A7+LMY+NSaPYE@ugly> (raw)
In-Reply-To: <20230324191302.GB536967@coredump.intra.peff.net>
On Fri, Mar 24, 2023 at 03:13:02PM -0400, Jeff King wrote:
>On Fri, Mar 24, 2023 at 08:02:53PM +0100, Oswald Buddenhagen wrote:
>> maybe the operation just forgets to load the graph?
>
so i strace'd the thing, and there is indeed no appearance of
'commit-graph' in the log.
so i tried git log --graph ... and still nothing?!
and yes, core.commitgraph is true (originally absent, so same thing).
>That seems weird.
>
indeed.
so weird in fact, that i tried another repository. and it works!
so apparently something is wrong with my/the linux repository.
things i can imagine contributing to throwing it off somehow:
$ git remote -v
alsa git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git (fetch)
alsa git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git (push)
history git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git (fetch)
history git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git (push)
linux-mips git://git.linux-mips.org/pub/scm/ralf/linux (fetch)
linux-mips git://git.linux-mips.org/pub/scm/ralf/linux (push)
linux-wireless git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers (fetch)
linux-wireless git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers (push)
origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (fetch)
origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git (push)
ossi git@github.com:ossilator/linux.git (fetch)
ossi git@github.com:ossilator/linux.git (push)
(the linux-* remotes haven't been pulled for years.)
$ grep replace .git/packed-refs
a3628e41a9946c4fe93d9b2ae5906e1b2184fa8e refs/replace/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
>What version of Git are you using?
>
rather recent master. dogfeeding my contributions.
next prev parent reply other threads:[~2023-03-24 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 18:54 limiting git branch --contains Oswald Buddenhagen
2023-03-23 19:42 ` Junio C Hamano
2023-03-23 20:44 ` Oswald Buddenhagen
2023-03-24 17:23 ` Derrick Stolee
2023-03-24 18:15 ` Oswald Buddenhagen
2023-03-24 18:20 ` Derrick Stolee
2023-03-24 19:02 ` Oswald Buddenhagen
2023-03-24 19:13 ` Jeff King
2023-03-24 19:58 ` Oswald Buddenhagen [this message]
2023-03-24 20:45 ` Jeff King
2023-03-24 22:06 ` Oswald Buddenhagen
2023-03-25 6:30 ` Jeff King
2023-03-25 8:05 ` Oswald Buddenhagen
2023-03-24 19:10 ` Jeff King
2026-05-27 7:05 ` Kristofer Karlsson
2023-03-23 20:56 ` Felipe Contreras
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=ZB4A7+LMY+NSaPYE@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=git@vger.kernel.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 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.