John Porter writes:
>
>Aldo Calpini wrote:
>> this is a little tutorial about submitting patches
>> (should be added to a FAQ, or somewhere where it's handy
>
>I think this deserves its own page somewhere on
>dev.perl.org.
Seems like a good idea. I've ad
Aldo Calpini wrote:
> this is a little tutorial about submitting patches
> (should be added to a FAQ, or somewhere where it's handy
I think this deserves its own page somewhere on
dev.perl.org.
--
JohnDouglasPorter
__
Do You Ya
this is a little tutorial about submitting patches
(should be added to a FAQ, or somewhere where it's handy
for people like me that tends to forget everything :-).
if there's something missing or incorrect, feel free to
let me know:
1. do a diff -u of the file(s) you want to patc
On Mon, Jul 22, 2002 at 06:35:47PM +0100, Leon Brocard wrote:
> This is really handy. While writing up the Perl 6 summary I've noticed
> that there were a couple of patches which appear to have slipped
> though the gapes. Patch authors - if you follow the Parrot patch
> procedure we won't forget y
Aldo Calpini sent the following bits through the ether:
> this is a little tutorial about submitting patches
> (should be added to a FAQ, or somewhere where it's handy
> for people like me that tend to forget everything :-).
This is really handy. While writing up the Perl 6 summar
this is a little tutorial about submitting patches
(should be added to a FAQ, or somewhere where it's handy
for people like me that tend to forget everything :-).
if there's something missing or incorrect, feel free to
let me know:
1. do a diff -u of the file(s) you want to patch
(n
Steve Fink wrote:
>
> Unrelated note for Jeff G: speaking of weird bounces, I can't seem to
> get any mail to you. For example, I sent a message warning that you
> hadn't cvs added hash.c and hash.h, and I'm pretty sure you never got
> it. A week or two ago, I got a bounce message back for anothe
Steve Fink writes:
>What about followups? The way I've settled on doing things is to send
>only to the bugs address initially, but then reply to both bugs and
>the list for any followup correspondence. I know that replying to just
>the bugs address isn't enough because it only forwards the initial
On Wed, May 15, 2002 at 01:20:21PM -0700, Robert Spier wrote:
>
> When submitting patches through the bugtracker, please do not CC the
> list as well. (This leads to duplicate tickets, because people reply
> to the non-managed version and CC the tracker etc.)
>
> the bugtra
When submitting patches through the bugtracker, please do not CC the
list as well. (This leads to duplicate tickets, because people reply
to the non-managed version and CC the tracker etc.)
the bugtracker (http://bugs6.perl.org) automagically sends new tickets
to the list.
If you have any
10 matches
Mail list logo
