git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/WIP] Pluggable reference backends

From
Max Horn <max@quendi.de>
Date
Mar 10, 2014, 15:51 UTC
Message-ID
<84EEAF2D-BCEA-4D02-95BE-31E9C518A0BC@quendi.de>
In-Reply-To
<CAJo=hJtiPgByhk9M4ZKD98DARzgeU6z2mmw7fcLTEbBza-_h6A@mail.gmail.com>
On 10.03.2014, at 15:30, Shawn Pearce <spearce@spearce.org> wrote:
Show 5 quoted lines
> On Mon, Mar 10, 2014 at 4:00 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
>> I have started working on pluggable ref backends.  In this email I
>> would like to share my plans and solicit feedback.
> 
> Yay!
Yay, too!
Show 12 quoted lines
> JGit already has pluggable ref backends, so it is good to see this
> starting in git-core.
> 
> FWIW the Gerrit Code Review community is interested in this project.
> 
>> * Store references in a SQLite database, to get correct transaction
>>  handling.
> 
> No to SQLLite in git-core. Using it from JGit requires building
> SQLLite and a JNI wrapper, which makes JGit significantly less
> portable. I know SQLLite is pretty amazing, but implementing
> compatibility with it from JGit will be a big nightmare for us.
I understood this as an example (indeed, it is listed under "Wile new ideas"), not a proposal to put this into the git core. It might be an interesting experiment in any case, and if the proposed modularity is truly achieved, it could (if there was any interest in it, that is) be implemented in an external 3rd party project.
Anyway, I am quite excited about this project. Usually, I am quite skeptical about such large scope ideas ("Yeah, cool idea, but who will pull it off, and with which resources?"). But this one seems to have a good chance of being implemented gradually and inside the main repository, with the help of "feature flags". 
Thus, I am looking forward to Michael's announced initial patch series. I feel that I don't know enough yet about git overall to be of much help on my own at this point. But perhaps over time some mini- or micro-projects pop up were others can help (e.g. "adapt these 50 tests to work with the 'quagga' ref"); if they are pointed out (assuming that doing so isn't more work than just addressing them yourself ;-), I am willing to help out.

Cheers, Max

Previous: Shawn PearceNext: Jeff King
Message 4 of 17 in “[RFC/WIP] Pluggable reference backends”
  1. Michael HaggertyMar 10, 2014
  2. Johan HerlandMar 10, 2014
  3. Shawn PearceMar 10, 2014
  4. Max HornMar 10, 2014
  5. Jeff KingMar 10, 2014
  6. David KastrupMar 10, 2014
  7. David LangMar 10, 2014
  8. Jeff KingMar 10, 2014
  9. David KastrupMar 10, 2014
  10. Junio C HamanoMar 10, 2014
  11. Jeff KingMar 10, 2014
  12. Michael HaggertyMar 10, 2014
  13. Shawn PearceMar 11, 2014
  14. egit vs. git behaviour (was: [RFC/WIP] Pluggable reference backends)Andreas Krey, Mar 12, 2014
  15. Shawn PearceMar 12, 2014
  16. Karsten BleesMar 11, 2014
  17. Michael HaggertyMar 12, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.