cp index.php index.php-20250220That last one is more common than I’d like, a lot more
Oh I used to do it as a kid
cd ~/repos/work-project27 git checkout dev git branch new_feature ### code for a few hours, close laptop, go to sleep, next morning git checkout dev ### code for a few more hours, close laptop go to sleep, next morning ## "oh fuck, I already implemented this in new_feature but differently" git checkout dev git diff new_feature ## "oh no. oh no no no. oh fuck. I can't merge any of this upstream and my history is borked." git clone git@workhub:work/work-project work-project28 cd ~/repos/work-project28cp $fic $fic.$(date -Iseconds) git commit -a -m "save at $(date -Iseconds)" # edit $fic git commit -a -m "save at $(date -Iseconds)" git push -fcp?💀
cp is short for create packup
The last is just a normal git workflow, isn’t it?
I’m pretty sure it means, they copy and paste the project file and iterate the version number manually.
The last one can easily describe Django. Feels like depending on the code base/your mistakes/people you work with can easily turn a normal project into a project where majority of the files is just migration files.
At university there were some students that want to manage projekts in could storange. That was just stupid but i didn’t know it better at that time.
I’m sick…that’s my excuse…
Didn’t want to be mean with the meme
Don’t worry, it’s fun
It’s quantum stuff, I could do that, or I could not do that…
Why did you mention git twice?
While TFS did support Git, I had to deal with the much worse TFVC for a long while, up until Azure DevOps came along.
MyProject - Copy v2.bak new NEW (3)/
And when it’s release, then you rename it to
MyProject - Copy v2.bak new NEW (3) FINAL.2-19-24/and then at the next standup, we all ponder how we can rename it to
MyProject - Copy v2.bak new NEW (3) FINAL.2/19/24/because the team lead needs m/d/yy names with forward slashes
It’s actually a pretty good idea to have a full system snapshot time to time, where the project can compile successfully, for future Virtual Machine use. It’s usually easier to spin a VM than setting up the whole dev environment from scratch.
Couldn’t add perforce to the list because someone else was checking it out, I see.
btrfs sub snap -rIsn’t that just git with more steps and harder to share?
It’s equivalent to
cp -r, but:- the copy is read-only
- reuses unchanged files
- easier to share (
btrfs sub send)
Sounds just like git (unless you do some special operations to change the copies)
With properly configured subvolumes, I’ll allow it.
I do miss the tags of SVN that would replace certain strings on each commit such as the date, a version number, etc.
CVS is gonna make a comeback! I tell ya!
No love for cvs?
