Paul Fenwick dijo [Tue, Nov 18, 2008 at 09:13:38PM +1100]:
G'day everyone,
I got stalled slightly by having a big hunk of work land on me, but I'm
looking through dh-make-perl again now. I've noticed that the indenting and
bracing tends to wander around a bit, which can make the program
Damyan Ivanov dijo [Tue, Nov 18, 2008 at 01:19:14PM +0200]:
If you still feel like re-indenting the whole file, send that as
a separate patch (perhaps before the real/functional patch).
Completely agree with this.
--
Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244
PGP key
-=| Paul Fenwick, Wed, Nov 19, 2008 at 12:25:50AM +1100 |=-
gregor herrmann wrote:
I think it would be helpful if someone cleaned up the file and
changed it to a consistent style. But I agree that it would be better
to have that before/separate from any substantial patch in order to
G'day everyone,
I got stalled slightly by having a big hunk of work land on me, but I'm
looking through dh-make-perl again now. I've noticed that the indenting and
bracing tends to wander around a bit, which can make the program flow hard
to follow in parts.
I'm hoping to standardise the code
-=| Paul Fenwick, Tue, Nov 18, 2008 at 09:13:38PM +1100 |=-
I got stalled slightly by having a big hunk of work land on me, but I'm
looking through dh-make-perl again now. I've noticed that the indenting and
bracing tends to wander around a bit, which can make the program flow hard
to follow
On Tue, 18 Nov 2008 13:19:14 +0200, Damyan Ivanov wrote:
I'm hoping to standardise the code layout, and wanted to check if we have a
preferred indentation level and bracing style? If not, I'll use the Perl
Best Practices recommendations of KR braces, uncuddled elses, 4-space
indents, and
gregor herrmann wrote:
I think it would be helpful if someone cleaned up the file and
changed it to a consistent style. But I agree that it would be better
to have that before/separate from any substantial patch in order to
make reviewing easier.
I'm very familiar with the idea of separating
G'day Gunnar, Mark, and anyone else reading this ticket.
Firstly, this is my first time responding to a Debian bug. If I've missed
something, or misunderstood the bug process, please let me know; I'm eager
to be educated.
I'm one of the Module::Install developers, and I've also been bitten by
On Sun, 16 Nov 2008 21:03:08 +1100, Paul Fenwick wrote:
Firstly, this is my first time responding to a Debian bug. If I've missed
something, or misunderstood the bug process, please let me know; I'm eager
to be educated.
That's fine, thanks for your comments.
I'm one of the
gregor herrmann dijo [Sun, Nov 16, 2008 at 03:18:15PM +0100]:
Firstly, this is my first time responding to a Debian bug. If I've missed
something, or misunderstood the bug process, please let me know; I'm eager
to be educated.
That's fine, thanks for your comments.
I also want to thank
-=| Gunnar Wolf, Sun, Nov 16, 2008 at 09:46:52AM -0600 |=-
I cannot recall the exact details... But I do recall there was a
reason for using M::D::I instead of META - I am just guessing, but I
think it is related to Paul's statement, «all modern CPAN modules
should have a META.yml file». Very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G'day everyone,
Quick policy check for me: Should I be replying just to the bug, or to
everyone, including the bug? At the moment I'm assuming the former, with
apologies to Gunnar, who's receiving this message twice. ;)
(Also apologies to
Gunnar
On Mon, 17 Nov 2008 09:42:25 +1100, Paul Fenwick wrote:
Quick policy check for me: Should I be replying just to the bug, or to
everyone, including the bug? At the moment I'm assuming the former, with
apologies to Gunnar, who's receiving this message twice. ;)
In this case replying to the bug
13 matches
Mail list logo
