News for hackers. Stuff that matters.

A comment on SQLite Doesn't Use Git. Parent comment

Re:SQLite Doesn't Use Git by thunderbong on Monday September 12, 2022 @08:47AM (#32809310)
It does, but in a roundabout way. You can create a private branch, keep committing to it and when you're ready, merge it to the public branch with a single commit message.

IMHO, this solves all issues in a very elegant way - my local repository shows all the commits (both private and public) but everyone else's shows all the commits as intended by the developers. Additionally, the public history is maintained consistently without wondering if someone messed it up.

https://www.fossil-scm.org/home/doc/4d8aecdf/www/private.wik...

[ Parent | on HN ]
Re:SQLite Doesn't Use Git by int_19h on Monday September 12, 2022 @11:00AM (#32811359)
Very interesting, thank you! Unfortunately, the doc page doesn't make it clear that the merge would produce a single commit; I wish this was clearer.

Also, do I understand it correctly that it's a single branch named "private" per repo?

[ Parent | on HN ]
Re:SQLite Doesn't Use Git by bonzini on Monday September 12, 2022 @11:20AM (#32811688)
Squashing the whole development in a single commit will lose granularity though, and make it hard to review the changes later. You could just use quilt (patch queues) for development, it's not optimal to have two tools though.
[ Parent | on HN ]
Re:SQLite Doesn't Use Git by the_duke on Monday September 12, 2022 @11:00AM (#32811353)
How wouod you do code reviews then?

Git style mailing of patches?

[ Parent | on HN ]