SVK::Co...d::Merge(3)

πŸ“¦
version 2.2.3 Β· 2 versions
, in fedora 43

πŸ’– SVK::Command::Merge β€” ok bestie, let's talk merging πŸ’–

So like… this page lives in the SVK::Command::Merge section of the User Contributed Perl Documentation, and it's literally all about applying the differences between two sources. Glow-up for your depot, fr fr. πŸ¦‹


✨ SYNOPSIS ✨

Here's the vibe, in three flavors:

merge -r N:M DEPOTPATH [PATH]
merge -r N:M DEPOTPATH1 DEPOTPATH2
merge -r N:M [--to|--from] [PATH]

Pick whichever one matches your situation, bestie. No wrong answers (well, okay, some wrong answers). πŸ’…


🌸 OPTIONS 🌸

Okay so here's the whole menu, every single one, no skips:

  • -r, --revision N:M β€” act on revisions between N and M. The classic. The blueprint. πŸ‘‘
  • -c, --change N β€” act on change N (which lives between revisions N-1 and N). And here's the lil plot twist: using -N reverses the changes made in revision N. Iconic behavior honestly.
  • -I, --incremental β€” apply each change individually. One at a time, like a careful queen. ✨
  • -a, --auto β€” merge from the previous merge point. It just knows where you left off, bestie.
  • -l, --log β€” use logs of merged revisions as the commit message. Let the history speak for itself. πŸŽ€
  • -s, --sync β€” synchronize mirrored sources before operation. Gotta sync before you slay. 🌈
  • -t, --to β€” merge to the specified path. Direction: to. ➑️
  • -f, --from β€” merge from the specified path. Direction: from. ⬅️
  • --summary β€” display related logs in this merge. Receipts, basically. 🧾
  • --verbatim β€” verbatim merge log without indents and header. Raw. Unfiltered. No filter. 🫢
  • --no-ticket β€” do not record this merge point. It never happened, as far as the merge points are concerned. πŸ’€
  • --track-rename β€” track changes made to renamed node. Because your renamed file still has lore. πŸ¦‹
  • -m, --message MESSAGE β€” specify commit message MESSAGE. Say what you mean.
  • -F, --file FILENAME β€” read commit message from FILENAME. For when your message is too long for the command line, which is valid.
  • --template β€” use the specified message as the template to edit. A lil starting point, then you make it yours. πŸ’–
  • --encoding ENC β€” treat -m/-F value as being in charset encoding ENC. Charset check!! 🌟
  • -P, --patch NAME β€” instead of commit, save this change as a patch. Not committing, just saving the evidence. πŸ’…
  • -S, --sign β€” sign this change. Put your name on it, main character. ✍️
  • -C, --check-only β€” try operation but make no changes. A dress rehearsal, no cap. πŸ‘€
  • --direct β€” commit directly even if the path is mirrored. Straight to the source, no detour. πŸ”₯

πŸ’œ A lil sign-off πŸ’œ

This page is from the User Contributed Perl Documentation, and it's running on perl v5.42.0, dated 2025-07-25. So if you were wondering what era of chaos this manual is from β€” that's the era. Slay, bestie, go merge something. πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from