Need help?
<- Back

Comments (35)

  • tonnydourado
    That was an informative post but Jesus Christ on a bicycle, reign in the LLM a bit. The whole thing was borderline painful to read, with so many "GPTisms" I almost bailed out a couple of times. If you're gonna use this stuff to write for you, at least *try* to make it match a style of your own.
  • spit2wind
    > only a handful of VCS besides git have ever managed a full import of the kernel's history. Fossil (SQLite-based, by the SQLite team) never did.I find this hard to believe. I searched the Fossil forums and found no mention of such an attempt (and failure). Unfortunately, I don't have a computer handy to verify or disprove. Is there any evidence for this claim?
  • tombert
    If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff.Obviously that's not surprising considering its creator, but hearing that was kind of the first time I had ever considered that you could translate something like Git semantics to a relational database.I haven't played with Pgit...though I kind of think that I should now.
  • corbet
    I hate to blow our own horn, but I'm gonna...if you are interested in seeing this kind of kernel-development data mining, fully human-written, LWN posts it every development cycle. The 6.17 version (https://lwn.net/Articles/1038358/) included the buggiest commit and much surrounding material. See our kernel index (https://lwn.net/Kernel/Index/#Releases) for information on every kernel release since 2.6.20.Or see LWN on Monday for the 7.0 version :)
  • niobe
    Very cool
  • gurjeet
    Technically correct title would be: s/Kernel into/Kernel Git History into/ Pgit: I Imported the Linux Kernel Git History into PostgreSQL
  • JodieBenitez
    Read the title and immediately thought "what a weird way to solve the performance loss with kernel 7..." The mind tricking itself :)
  • srslyTrying2hlp
    [dead]
  • QuiCasseRien
    [flagged]