Hacker News new | past | comments | ask | show | jobs | submit login

Two concepts are bound up together in a commit. "Publish" and "Save".

In general our OSes aren't storing a complete history of a file, so we rely on git "quick saves" (as someone else put it).

The git log is as much an artifact of the development process as the ticket history or the code itself. You don't want to publish your quick saves for someone else to have to dig through in two years time - give them something a bit more polished than that.




That distinction should be part of Git. For now, we may rely on wip branches for "save" and merging them into master for "publish".


I thought that too, but in writing that comment I realised "save" should actually be part of the filesystem.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: