Astro Hacker News - I imported the full Linux kernel git history into pgit

tonnydourado |next [-]

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.

vidarh |root |parent |next [-]

To add a tip on how to make it match your own style: You can get decently far by pointing it to a page or so of your own writing, and simply tell it to review the post section by section and edit it to match the tone and style of the example. It's not perfect by any means, but it will tend to edit out the type of language you're not likely to use, so really to make it sound less LLM-like, almost any writing sample from a human author works.

darkwater |root |parent |next |previous [-]

100% agreed. Maybe this inner reaction will disappear over the years of being exposed to the GPT writing style, or maybe LLMs will be "smarter" on this regard, and being able to use different styles even by default. But I had the same exact feelings as you reading this piece.

vidarh |root |parent [-]

It's really simple to fix by asking an LLM to apply a style from a sample, so my guess is a lot of product will build in style selection, and some provider will add more aggressive rules in their system prompts over time.

consp |root |parent |previous [-]

I stopped at "pgit handled it.". The tldr was appreciated though as now I don't have to sieve though the LLM bloat.

tombert |next |previous [-]

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.

anitil |root |parent |next [-]

The sqlite project actually benefited from this dogfooding. Interestingly recursive CTEs [0] were added to sqlite due to wanting to trace commit history [1]

[0] https://sqlite.org/lang_with.html#recursive_query_examples

[1] https://fossil-scm.org/forum/forumpost/5631123d66d96486 - My memory was roughly correct, the title of the discussion is 'Is it possible to see the entire history of a renamed file?'

anitil |root |parent [-]

On and of course, the discussion board is itself hosted in a sqlite file!

20after4 |root |parent |next |previous [-]

When you import a repository into Phabricator, it parses everything into a MySQL database. That's how it manages to support multiple version control systems seamlessly as well as providing a more straightforward path to implementing all of the web-based user interface around repo history.

adastra22 |root |parent |next |previous [-]

Git was a (poor) imitation of the monotone DVCS, which stored its data in sqlite.

xeubie |root |parent [-]

True, git poorly imitated monotone's performance problems.

gjvc |root |parent |previous [-]

"If I recall correctly, the Fossil SCM uses SQLite under the covers for a lot of its stuff."

a fossil repository file is a .sqlite file yes

ptdorf |root |parent |next [-]

So SQLite is versioned in SQLite.

yjftsjthsd-h |root |parent [-]

Yep:) To be fair, I expect git to be stored in git, mercurial to be in mercurial, and... Actually now I wonder how svn/cvs are developed/versioned.

deepsun |root |parent [-]

SVN in SVN for sure, it's a well made product. The market just didn't like it's architecture/UX that doctates what features available.

CVS is not much different from copying files around, so would not be surprised if they copied the files around to mimic what CVS does. CVS revolutionized how we think of code versioning, so it's main contribution is to the processes, not the architecture/features.

vidarh |root |parent [-]

The market did like it just fine until Git came around. It just had a very brief moment in the sun....

tombert |root |parent |previous [-]

Makes sense, I haven't used the software in quite awhile.

niobe |next |previous [-]

Very cool

gurjeet |next |previous [-]

Technically correct title would be: s/Kernel into/Kernel Git History into/

    Pgit: I Imported the Linux Kernel Git History into PostgreSQL

worldsayshi |root |parent [-]

Wow that has a very different meaning from what I thought.

JodieBenitez |next |previous [-]

Read the title and immediately thought "what a weird way to solve the performance loss with kernel 7..." The mind tricking itself :)

srslyTrying2hlp |next |previous [-]

[dead]

QuiCasseRien |previous [-]

[flagged]