Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gix-ref: ref-table backend (research) #109

Open
Byron opened this issue Jun 25, 2021 · 7 comments
Open

gix-ref: ref-table backend (research) #109

Byron opened this issue Jun 25, 2021 · 7 comments
Labels
C-tracking-issue An issue to track to track the progress of multiple PRs or issues

Comments

@Byron
Copy link
Member

Byron commented Jun 25, 2021

It's not in mainline yet, but definitely kind of on the way and available.

I thought I saw it show up once in the mainline git repository, but it's definitely not there anymore.

@Byron Byron changed the title git-ref: ref-table backend _(research)_ git-ref: ref-table backend (research) Jun 25, 2021
@Byron Byron added the C-tracking-issue An issue to track to track the progress of multiple PRs or issues label May 15, 2022
@Byron Byron changed the title git-ref: ref-table backend (research) gix-ref: ref-table backend (research) Sep 4, 2023
@KarthikNayak
Copy link

@kamulos
Copy link

kamulos commented May 24, 2024

This would be quite nice if supported. Just out of curiosity I used --ref-format=reftable when cloning some repos, but my starship prompt cannot show most information about the repo (for example which branch I am on).

@Byron
Copy link
Member Author

Byron commented May 25, 2024

Thanks for the heads-up! It will definitely take a while until this becomes priority, as it will only really be needed when gitoxide gets to the server side.

@KarthikNayak
Copy link

Thanks for the heads-up! It will definitely take a while until this becomes priority, as it will only really be needed when gitoxide gets to the server side.

Reftables can be used on the client side too. Like @kamulos mentioned, clients like starship would already break.

@Byron
Copy link
Member Author

Byron commented May 25, 2024

I am quite aware - however, those most interested would be servers, or users with huge monorepos. The latter are probably missing more features than just ref-table at the moment, so it will take a while. Ordinary use-cases don't have benefits switching to ref-table, as it makes the ref-database more obscure.

@KarthikNayak
Copy link

Yup, that I agree with. There is also talks about making it default a lot later, something to keep an eye out for https://lore.kernel.org/git/84c01f1b0a2d24d7de912606f548623601c0d715.1716555034.git.ps@pks.im/

@Byron
Copy link
Member Author

Byron commented May 25, 2024

Thanks! Please keep me posted about this. I definitely hope they won't make it default anytime soon, that would force my hand 😅.
Thinking about it - the ton of Git libraries out there would all have to struggle to get that implemented, so my feeling is they will just keep what's working well by now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue An issue to track to track the progress of multiple PRs or issues
Projects
None yet
Development

No branches or pull requests

3 participants