CVSQ-MERGE(1)

πŸ“¦ version 1.11, in nixos 26.05, nixpkgs unstable

πŸ’… CVSQ-MERGE πŸ’…

okay so this is cvsq-merge(1) β€” section 1 of the manual, bestie, write it down πŸ“ β€” and it's the little helper that sets up your merge files when a change got yeeted onto a branch through cvsq-branch.


✨ NAME ✨

cvsq-merge β€” set up the files you need to merge in a change that went to a branch via cvsq-branch. that's the whole job, and it eats every time 🫢


πŸŽ€ SYNOPSIS πŸŽ€

cvsq-merge [-l] .<tag>

🌸 DESCRIPTION 🌸

okay so picture this: you just did an update, and you find a file named .cvsq-branch-... sitting there. that file is literally the vibe check telling you a commit got redirected to a branch via cvsq-branch(1) πŸ‘‘

usually that's exactly when cvsq-merge gets called β€” with that file name as its argument. and what it does is lowkey iconic: it sets up two symbolic links, .origin and .branch, pointing at a copy of the working directory, updated to the beginning and the end of the identified branch. two copies, two eras, one merge. periodt πŸ’…

so how do the two ends get made?

  • the beginning of the branch β€” it copies the current directory and calls cvs update -r<tag>-start inside that copy 🌱
  • the end of the branch β€” it copies the current directory and calls cvs update -r<tag> inside that copy 🌳

same recipe, different tag suffix. not me thinking that's actually so clean 😭


πŸ”₯ OPTIONS πŸ”₯

  • -l β€” use lcvs(1) instead of cvs(1) to update the copies of the working directory. one tiny flag, whole different tool, iykyk ✨

πŸ¦‹ FILES πŸ¦‹

  • ~/.cvsq-branch/merge/<tag> β€” this directory is where the magic lives. it contains the subdirectories origin and branch, and those hold a copy of the working directory updated to the beginning and the end of the branch respectively. two little folders, both main character energy πŸ’–

🌈 SEE ALSO 🌈

cvsq-branch(1), lcvs(1), cvsq(1), cvs(1)

go read the whole friend group, fr fr 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Klaus Aehlig <aehlig@linta.de> β€” the icon who made all this happen πŸŽ€


ngl bestie, this one is short and sweet: find the .cvsq-branch-... file, hand it over, get your .origin and .branch symlinks, merge, slay. no cap πŸ’€βœ¨

that's the whole page, bestie β€” cvsq-merge(1), dated April 24, 2007, and yeah the header and footer both just say CVSQ-MERGE(1) because that's how manpages roll πŸ’œ see you in the next one, mwah πŸ“

πŸ“¦ where this page comes from