this post was submitted on 31 Jul 2025
24 points (96.2% liked)

General Programming Discussion

8899 readers
7 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 6 years ago
MODERATORS
Cloak@lemmy.ml
Restioson@lemmy.ml
24
Worktrees: Git's best kept secret (and why you should use them) | Tom Ups (www.tomups.com)
submitted 1 month ago by dessalines@lemmy.ml to c/programming@lemmy.ml
20 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] eldavi@lemmy.ml 1 points 1 month ago (1 children)

every time i do this, i have to annotate the old copy somehow.

i usually use a date and months later i have no clue why i made the copy.

[–] SpaceNoodle@lemmy.world 3 points 1 month ago (1 children)

Yes, you should name directories descriptively. I don't think that's unique to repository clones.

[–] eldavi@lemmy.ml 1 points 1 month ago (1 children)

definately not since that's the way i learned.

the problem is that a directory named master-hotfix-vgpool01-05022022 is very difficult to remember why it was created if you looked at it today.

[–] SpaceNoodle@lemmy.world 2 points 1 month ago (1 children)

Then clearly it was poorly named.

[–] eldavi@lemmy.ml 0 points 1 month ago (1 children)

so what would you name it?

[–] SpaceNoodle@lemmy.world -1 points 1 month ago

Something that clearly communicates its purpose.