All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Karthik Nayak <karthik.188@gmail.com>,
	K Jayatheerth <jayatheerthkulkarni2005@gmail.com>,
	ryenus@gmail.com, git@vger.kernel.org
Subject: Re: Re [bug] pull --prune could not delete references due to lock file already exists error
Date: Wed, 2 Jul 2025 10:50:58 +0200	[thread overview]
Message-ID: <aGTy8qX9uvwWv_ap@pks.im> (raw)
In-Reply-To: <xmqqtt3vkhwk.fsf@gitster.g>

On Tue, Jul 01, 2025 at 09:14:19AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> > I bet there's also tons of scripts out there that just reach into the
> > filesystem to do stuff, but that's something that we cannot really help
> > with.
> 
> I thought you've done enough to make sure that common things people
> would want to do by direct access to the .git/refs/ hierarchy can be
> easily done with plumbing commands instead, so it would probably be
> a matter of writing and publicizing the "how to migrate to the world
> where you cannot write into files under .git/refs/ directory"
> document?

Yeah, all the tools are there. I'm not even sure whether such a guide
would be required in the first place -- tools are just what you are used
to already anyway. So I don't know whether I really need to explain how
to use git-update-ref(1) and friends.

I am of course biased here, so if disagree and think that this would be
required I might just do it.

Anyway, I'll hack something up and send it to the mailing list soonish
to get the discussion going.

Patrick

  reply	other threads:[~2025-07-02  8:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 12:32 [bug] pull --prune could not delete references due to lock file already exists error ryenus
2025-06-25 14:18 ` Re " K Jayatheerth
2025-06-27 18:59   ` brian m. carlson
2025-06-30  7:26     ` JAYATHEERTH K
2025-06-30 13:46   ` Karthik Nayak
2025-06-30 14:20     ` brian m. carlson
2025-06-30 21:10       ` Junio C Hamano
2025-07-01 10:31         ` Patrick Steinhardt
2025-07-01 16:14           ` Junio C Hamano
2025-07-02  8:50             ` Patrick Steinhardt [this message]
2025-07-01  8:20       ` Karthik Nayak
2025-07-02  4:50       ` Chris Torek
2025-07-02 15:37         ` Junio C Hamano
2025-07-01  0:52     ` JAYATHEERTH K

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=aGTy8qX9uvwWv_ap@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jayatheerthkulkarni2005@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=ryenus@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /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.