From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Cc: Bence Ferdinandy <bence@ferdinandy.com>,
git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: branch description as a note?
Date: Thu, 12 Dec 2024 11:48:35 +0100 [thread overview]
Message-ID: <Z1q_gyUlnWiVtc7P@ugly> (raw)
In-Reply-To: <07e3a0a3-7551-4f54-bc3c-afd8dae7da02@app.fastmail.com>
On Wed, Dec 11, 2024 at 11:07:55PM +0100, Kristoffer Haugsbakk wrote:
>On Wed, Dec 11, 2024, at 21:13, Kristoffer Haugsbakk wrote:
>> See also this project idea https://github.com/gitgitgadget/git/issues/438
>>
>> Which also links to a 2019 thread.
>>
>> With +CC on the participants. I hope that’s okay.
>
>Reiterating what I wrote there
>
>https://github.com/gitgitgadget/git/issues/438#issuecomment-2381017430
>
>I would store all ref metadata in one ref. Either divide it
>up into files or have one structured file. I’ve seen this idea
>floating around. I haven’t seen any purpose-built tools for it yet.
>
https://wiki.qt.io/Git-gpush-scripts does exactly that, but putting a
state file into a special ref.
this script suite can be used to address bence's use case of migrating
wip state between machines, by having a git remote for the "magic" ref
space.
it's not perfect for a patch-based workflow, as i bolted it on as an
afterthought. and it could also use a github-centered mode. patches
welcome.
prev parent reply other threads:[~2024-12-12 10:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:39 branch description as a note? Bence Ferdinandy
2024-12-11 16:11 ` Junio C Hamano
2024-12-11 17:37 ` Konstantin Ryabitsev
2024-12-11 22:11 ` Bence Ferdinandy
2024-12-12 1:39 ` Junio C Hamano
2024-12-12 2:30 ` Konstantin Ryabitsev
2024-12-11 21:57 ` Bence Ferdinandy
2024-12-12 1:00 ` Junio C Hamano
2024-12-12 10:48 ` Bence Ferdinandy
2024-12-11 17:34 ` Justin Tobler
2024-12-11 22:02 ` Bence Ferdinandy
2024-12-12 1:52 ` Junio C Hamano
2024-12-12 10:57 ` Bence Ferdinandy
2024-12-11 20:13 ` Kristoffer Haugsbakk
2024-12-11 22:07 ` Kristoffer Haugsbakk
2024-12-12 10:48 ` Oswald Buddenhagen [this message]
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=Z1q_gyUlnWiVtc7P@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=liu.denton@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).