Working-copy-as-a-commit - convergent thought

[goyalyashpal]

woww, i am no expert in vcs, infact have used only git on 2 personal projects of 1-2 mo duration each so far.

but even in that small duration too, i reached at same conclusion. that working copy should be deal as a commit. my thought too was that it would save hassle in moments where you have to checking out the staged code (say for building some more source to commit) etc...

in stock git, it's so much of a hassle to stash but remember no to change index, then perform task, stage, commit, then stash pop --- ugh...

and today, i found it here that someone has already thought same and has implemented it too😄
niice :)

recorded automatically

jj/README.md

Lines 76 to 80 in ac3d1a8

	- **Working-copy-as-a-commit**: Changes to files are [recorded automatically][wcc]
	as normal commits, and amended on every subsequent change. This "snapshot"
	design simplifies the user-facing data model (commits are the only visible
	object), simplifies internal algorithms, and completely subsumes features like
	Git's stashes or the index/staging-area.

---

P.S. I came here via this link https://news.ycombinator.com/item?id=34306260 via x