Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:a git repo (Score 1) 168

Git stashes (I believe) cannot be pushed to another computer, so they are useless for this purpose. So, as you recognize, the choice is between "remember to commit && push every time you leave the workstation, and then always rewrite history because otherwise git bisect won't work" or "install Dropbox, do nothing else and it just works(tm)". That is not what I do, but I can totally understand people going for the second option.

Comment Re:a git repo (Score 1) 168

You probably don't understand their use case. This is a single person, working both from a workstation (when they are at work) or from a laptop (when they telecommute, or are away, or...). At any point in time they may have to leave the workstation in a hurry, and they want to resume coding on the laptop as if they were on the same computer. They don't want to commit, not even to a private branch, because when they have to leave the code may not even compile. Of course, their code needs to be in a git repo to interact with the rest of the world. So, what's the solution? Stick your git repo inside Dropbox. The Dropbox "Last change wins" semantic is fine, because there is a single user: they won't sit in front of two different keyboards at the same time (and it is reasonable to assume that the laptop is always going to be online). It sounds stupid, I agree, but it works for them, so who am I to disagree?

Comment Re:a git repo (Score 1) 168

git doesn't sync continuously across machines, it syncs only when you commit. If you work on multiple computers (such as a laptop and a workstation), you may want to sync continuously à la Dropbox. I even know people who keep their git repo inside Dropbox -- I know, it sounds stupid.

Slashdot Top Deals

Were there fewer fools, knaves would starve. - Anonymous