On Sun, 24 Dec 2006 10:53:03 -0600 Josh Paetzel wrote:
> I'm in the process of writing a port and it has a dependancy that's
> not in the ports tree, so I'm porting that as well. My question is
> what's the procedure in such a case? Should I submit them both as
> part of the same pr? Obvious
Josh Paetzel schrieb:
I'm in the process of writing a port and it has a dependancy that's
not in the ports tree, so I'm porting that as well. My question is
what's the procedure in such a case? Should I submit them both as
part of the same pr? Obviously the one can't be committed without
th
On Sun, Dec 24, 2006 at 10:53:03AM -0600, Josh Paetzel wrote:
> I'm in the process of writing a port and it has a dependancy that's
> not in the ports tree, so I'm porting that as well. My question is
> what's the procedure in such a case? Should I submit them both as
> part of the same pr? O
Josh Paetzel <[EMAIL PROTECTED]> wrote:
>
> I'm in the process of writing a port and it has a dependancy that's
> not in the ports tree, so I'm porting that as well. My question is
> what's the procedure in such a case? Should I submit them both as
> part of the same pr? Obviously the one can
I'm in the process of writing a port and it has a dependancy that's
not in the ports tree, so I'm porting that as well. My question is
what's the procedure in such a case? Should I submit them both as
part of the same pr? Obviously the one can't be committed without
the other.
--
Thanks,