3 ms·
Per "git undo", what about something like: git rewind git rewind FILE git rewind --revision=REVISION git rewind FILE --revision=REVISION
by mintplant 15y ago
Per "git undo", what about something like:
git rewind
git rewind FILE
git rewind --revision=REVISION
git rewind FILE --revision=REVISION
We already have the "fast forward" metaphor.
- eridius 15y agoInteresting idea, though I don't get the need for the --revision flag in your example. It's already pretty easy to tell the difference between revisions and files. If you want to call it unwind, why not just make that an alias for reset? git config alias.rewind reset
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]
- mintplant 15y agoAh, okay. Wasn't sure how well the system could differentiate the two. You could always make aliases for things, but the point of the article seems to be addressing the problem of people new to git, who likely won't go about setting such aliases, let alone know they have that capability. And that's a problem I can sympathize with: I'm a programmer on an FRC (http://www.usfirst.org/ http://www.usfirst.org/) team, and this year, we finally convinced everyone to make the jump from a thousand USB sticks to a git repo. We've held a workshop on it and have distributed various tutorials -- GitHub's have been particularly invaluable -- but there are still issues every now and again. Some seem to only have "push button, receive outcome" understanding of how it works, memorizing the commands for cloning, pushing, and pulling and then blindly repeating them into the console, without a full knowledge of what's going on. If some of the more "advanced" syntax was a bit more human from the get-go, then it might be helpful in softening the learning curve.