News for hackers. Stuff that matters.

A comment on Why SQLite Does Not Use Git. Parent comment

Re:Why SQLite Does Not Use Git by philipwhiuk on Tuesday April 10, 2018 @08:33PM (#16807032)
When I make a change, I want to mark that the I changed 3 files simultaneously. Not that I intended the system to work with only the first file changed.

I don't claim that Git is perfectly. But most of the problems are solved by better UI (Git does track when files are renamed, created and deleted), not by wrecking what a commit is.

Git understands commits. CVS style 'every file has it's own history' is wrong. Git's not perfect and I would not be too bothered if Mecurial beats it long term, but my god if I had to go back to CVS-style flow with concept of multi-file checkin, I would quit my job.

[ Parent | on HN ]
Re:Why SQLite Does Not Use Git by cesarb on Tuesday April 10, 2018 @09:39PM (#16807338)
> Git does track when files are renamed, created and deleted

Actually, no, it doesn't. Git tracks just the before/after state: before the commit these files existed, after the commit those files existed. It infers creation/deletion/rename, when necessary, by comparing these two (or more) states.

[ Parent | on HN ]
Re:Why SQLite Does Not Use Git by emmelaich on Tuesday April 10, 2018 @11:09PM (#16807730)
Yeah it's not track it is infers

Which doesn't always work. Not that it matters.

[ Parent | on HN ]