Patches for a slave port

[Chris H]

On Sat, 16 Dec 2017 00:16:39 -0800 "Kevin Oberman" <rkoberman at gmail.com> said

> On Fri, Dec 15, 2017 at 7:19 AM, Chris H <portmaster at bsdforge.com> wrote:
> 
> > On Thu, 14 Dec 2017 20:53:38 -0800 "Kevin Oberman" <rkoberman at gmail.com>
> > said
> >
> > I am attempting to submit a fix for a slave port,
> >> multimedia/avidemux_plugins. All of the patches are in the master port,
> >> avidemux. So I make all of the fixes and run "make makepatch". All of the
> >> patches are generated into avidemux/files. I then ran "svn diff" in
> >> avidemux_plugins and the only thing generated is the removal of BROKEN.
> >> OK.
> >> The patches are in the master port, so I run "svn diff" there and no
> >> differences are shown. Huh?
> >>
> >> Why does "svn diff" not see the new files? How do I get the diffs? Or am I
> >> going to have to manually generate the diff the old fashioned way.
> >>
> > svn add, before running the diff?
> >
> >
> How many years (or decades) have I been using and even hacking CVS and
> Subversion? Oh, this is embarrassing!
Heh. Want to know that why that answer came so quickly to me?
Because, I too for get that. :-) It used to be so easy, back in the CVS
days. Those commands were the only ones you had to remember. Well, unless
you count RCS. Adding SVN, GIT, DARCS, ... -- enough, already!

There's *no* shame in forgetting, Kevin. :-)

--Chris
> 
> Thanks, Chris
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman at gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683