☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 8 months agoGit Ruleslemmy.mlimagemessage-square19fedilinkarrow-up1153
arrow-up1145imageGit Ruleslemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 8 months agomessage-square19fedilink
minus-squareBaby Shoggoth [she/her]@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up52·8 months ago“only one person per file” so we’ve reverted back to the rcs/cvs days?
minus-square👍Maximum Derek👍@discuss.tchncs.delinkfedilinkEnglisharrow-up7·8 months agoGLADOS was already attempting to digitize employees. And we all know you don’t concatenate employees, because the DIFFs become useless.
minus-square☆ Yσɠƚԋσʂ ☆@lemmy.mlOPlinkfedilinkarrow-up7arrow-down1·8 months agowelcome to Microsoft SourceSafe :)
minus-squaresjmulder@lemmy.sdf.orglinkfedilinkarrow-up2·8 months agoWe don’t even have that rule with CVS. Sometimes you have a merge conflict after cvs up, well then you fix it. That’s how it’s supposed to work.
“only one person per file”
so we’ve reverted back to the rcs/cvs days?
GLADOS was already attempting to digitize employees. And we all know you don’t concatenate employees, because the DIFFs become useless.
welcome to Microsoft SourceSafe :)
We don’t even have that rule with CVS. Sometimes you have a merge conflict after cvs up, well then you fix it. That’s how it’s supposed to work.