Follow Slashdot blog updates by subscribing to our blog RSS feed
Nickname:
Password:
I have my own simple and versatile way of keeping track of branches.
*Project*Copy of project*Copy of Copy of project*Copy of Copy of copy of project
That file naming convention is too predictable. Around here we use names like:winter-projectnov-15-projectproject-2.011.05.12-projectproject-somebodys-name
Which one is the most recent? Oh look at the last modified date for the file, of course.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
We have a equal opportunity Calculus class -- it's fully integrated.
PFT! Version control is for sissies. (Score:5, Funny)
I have my own simple and versatile way of keeping track of branches.
*Project
*Copy of project
*Copy of Copy of project
*Copy of Copy of copy of project
Re: (Score:2)
That file naming convention is too predictable. Around here we use names like:
winter-project
nov-15-project
project-2.0
11.05.12-project
project-somebodys-name
Which one is the most recent? Oh look at the last modified date for the file, of course.
Re:PFT! Version control is for sissies. (Score:1)
True, and so is the version control idea I stole:
age file
does "mv file file-; cp -p file- file" so you end up with files named "file" and "file-". age again and you get file, file- file--.
Which one is the most recent? In this example, it's always the file named "file".
Simple but very effective. However, I'm moving into the 21st century with git.