What

?
OK, did a bit of looking and here's what I get. Please let me know whether it's right.
Hypothetically, I'm packaging flurb 0.1. It has two problems: It blurfles, and a config path not correct for VL is hardcoded into the Makefile.
Because these are two different issues, I should create two separate patches.
I unpack the tarball into my working directory, resulting in flurb-0.1/ and its subdirectories . . . and begin.
me: $ mkdir flurb-0.1.blurflepatch # Make a directory for blurfle fixing
me: $ cp -a flurb-0.1/* flurb-0.1.blurflepatch # Copy original source there
me: $ mkdir flurb-0.1.config-path-patch # Separate directory for config path work
me: $ cp -a flurb-0.1/* flurb-0.1.config-path-patch # (there are other ways)
#Edit files in text editor
me: $ nano flurb-0.1.blurflepatch/examples/flurbrc # Make changes and save
me: $ nano flurb-0.1.config-path-patch/Makefile
# Make no other changes for now.
# The crux of the question: ###################################################################~
me: $ ls ; # Run diff from original working directory #
flurb-0.1/ flurb-0.1.blurflepatch/ flurb-0.1.config-path-patch/ #
#
diff -Naur flurb-0.1 flurb-0.1.blurflepatch >flurb-0.1-blurfle.patch #
diff -Naur flurb-0.1 flurb-0.1.config-path-patch >flurb-0.1-config-path-VL.patch #
# That one's slack-specific, so I chose to tag it "VL" #
Diff compares everything in flurb-0.1/ to what's in flurb-0.1.blurflepatch/ and outputs the differences between the files (just one, here) to the patch. Same thing for config path fix. I now have two patches ready to copy to my submission's src/patches.
Am I right?
Of course there are other ways to do these particular patches without copying over the whole source, etc. I'm just trying to get the basics down.
So the question is, will using diff this way result in valid patches ready for 'patch -p1 <(patchfile)' as used by sbbuilder-generated SlackBuilds?