On 9 November 2011 17:36, James wrote:
> Hello,
>
> A better method to review code?
>
You seem to be talking about doing a few different things, none of
which is _quite_ what I'd call a code review.
What you're currently doing makes sense if you're interested in
finding out what some code does b
On Wed, Nov 9, 2011 at 11:36 AM, James wrote:
> Hello,
>
> A better method to review code?
>
> I find myself having to audit the code inside
> of ebuilds in order to understand how a given
> piece of code has been changed.
>
> So what I do is go to the /usr/portage/distfiles
> and then use vi to l
Hello,
A better method to review code?
I find myself having to audit the code inside
of ebuilds in order to understand how a given
piece of code has been changed.
So what I do is go to the /usr/portage/distfiles
and then use vi to look at the file listing;
move up and down to select the file o
3 matches
Mail list logo
