TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Using WIP branches to save every edit

30 pointsby rlmover 15 years ago

6 comments

MartinMondover 15 years ago
It's a really useful time save.<p>Unfortunaly git-wip by default doesn't commit files that are untracked (e.g. new). I submitted a patch to do exactly this: <a href="http://github.com/MSch/git-wip/commit/22f4b57b67762a0123d1ba319e82a0bc2a4ce338" rel="nofollow">http://github.com/MSch/git-wip/commit/22f4b57b67762a0123d1ba...</a>
windsurferover 15 years ago
Why not have a daemon track for file state changes instead of having every editor run the <i>git wip</i> command? That would be much more general and probably better for most projects.<p>Maybe I'll make such a daemon...
评论 #1029095 未加载
评论 #1028766 未加载
评论 #1028954 未加载
skorguover 15 years ago
This is timely considering just last night I "rm -rf projectname.py" instead of "rm -rf projectname.sqlite". D'oh.
iveyover 15 years ago
Anyone have it working in Emacs? I may fool around with it tonight, if not, and see if I can get it working.
评论 #1029540 未加载
jed_sover 15 years ago
this should be integrated into editors as undo/redo<p>i've long thought proper version control makes sense if it's fast enough -- eventually everything will be tracked anyway.<p>it doesn't make any sense to lose any ideas just because only one of them was "the winner".
akkartikover 15 years ago
How does this compare with git stash?