[stiray]

Bit needs just one single switch and everyone will gladly use it for its killer feature.

Undo with one single command, without strange additional arguments, weird naming, strange documentation[1] etc.

[1]https://git-man-page-generator.lokaltog.net

When anyone is doing the "next best thing after bread and butter" version control, please start with --undo switch.

Sometimes you just need a hammer, without any will or need to learn how to make hammers.

[asdjlkadsjklads]

I'm writing a git-like, so i'm curious your thoughts on this. What would undo, do exactly?

Eg would it make a new commit, reverting the previous? Would it undo the last commit, dropping it from history? Would it undo the last commit, putting the contents into staging/unchecked?

My git-like is for structured data and is very very different from git. Conceptually though, it's similar in that it's a hash tree of content addresses. So it'll conceptually suffer the same problems, if i wanted it to.

My plan, due to the nature of the project, is to for the most part avoid conflicts and be more forgiving in the primary flows. This makes sense (imo) because the nature of the application is about data retention moreso than it is strictly VCS. It just has VCS fundamentals to reach into, should they be needed.

But as i dive into the primary user flow - it feels like there are always a few cases that seem primary. Undo is a great example - making a new commit (revert), undoing the last and dropping it (hard reset), and undoing the last into staging all seem like primary UXs.

A lot of Git feels like the primary UX. I struggle to think of single concepts, like your undo example, where a simple path will be right to the user 90% of the time.

Thoughts?

[renox]

IMO it's simple: with undo you want to 'go back in time' so you want to remove the commit and get the exact same list of staged/modified files that you had before (especially useful when you made a git commit -a which added too many files in the commit)

[j1elo]

> https://git-man-page-generator.lokaltog.net

Reading the summary and the first paragraphs, I've just processed a bunch of words that I understand by themselves, but bear no meaning to me when placed together. I guess the target audience is a bunch of very power users who would probably not need explanations anyway.

[purerandomness]

It's satire. It generates gibberish using actual words from git man pages. Its purpose was to show how important technical documentation is, and how the git man pages could be improved.

[j1elo]

D'Oh! It took me with the trolling detector off and I thought it really was talking about something! Nice one.

[lanstin]

also an undo for undo?