doublechecking: repocopy

just doublechecking so I don't muck up cvs: repocopy. ircd-ratbox-devel is at 3.0.7 (the official release now) maintainer has asked for a repocopy. I have assigned the pr to portmgr, with state of 'open' (should it have been feedback?) once repocopy is done and assigned back to me, I do a cvs

Re: doublechecking: repocopy

On 14 April 2012 09:57, Michael Scheidell wrote: > just doublechecking so I don't muck up cvs: > > repocopy. > ircd-ratbox-devel is at 3.0.7 (the official release now) > maintainer has asked for a repocopy. > I have assigned the pr to portmgr, with state of 'open' (should it have been > feedback?)

Re: doublechecking: repocopy

On 14 Apr 2012 14:57, "Michael Scheidell" wrote: > > just doublechecking so I don't muck up cvs: > > repocopy. > ircd-ratbox-devel is at 3.0.7 (the official release now) > maintainer has asked for a repocopy. > I have assigned the pr to portmgr, with state of 'open' (should it have been feedback?)

Re: doublechecking: repocopy

On 4/14/12 10:51 AM, Chris Rees wrote: Grab the PR back and just commit the new files in place. than it loses history of the -devel branch. I guess you can't keep it all.. PR taken back. Will think about it a little more. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporatio

Re: doublechecking: repocopy

On 4/14/12 10:51 AM, Chris Rees wrote: Grab the PR back and just commit the new files in place. and I am going to want to do something similar to p5-Mail-SpamAssassin. repocopy to -devel (isn't one yet), add ../mail/Makefile entry. edit/test/fix -devel for a while then copy it back over to

Re: doublechecking: repocopy

On 14/04/2012 15:51, Chris Rees wrote: On 14 Apr 2012 14:57, "Michael Scheidell" > wrote: > > just doublechecking so I don't muck up cvs: > > repocopy. > ircd-ratbox-devel is at 3.0.7 (the official release now) > maintainer has asked for a repocopy. > I have assig