On Tue, Aug 24, 2010 at 7:02 PM, brian d foy <brian.d.foy@gmail.com> wrote:
> In article
> <AANLkTinkUqcz0-Hw4DH74FHy6cEUiNnznBQR07YacyyU@mail.gmail.com>, Craig
> A. Berry <craig.a.berry@gmail.com> wrote:
>
>> In that case should the following entry in perl5122delta.pod be
>> changed to reflect the newest new canonical location?
>>
>> =item *
>>
>> The version of L<perlfaq> shipped with the perl core has been updated to the
>> latest official FAQ version as available at
>> L<git://github.com/briandfoy/perlfaq.git>.
>
> Well, it should point to whereever you synced it from.
Actually I didn't sync anything, you did:
http://perl5.git.perl.org/perl.git/commitdiff/d12d61c
and then Merijn requested that it get pulled to maint, and a couple of
us voted +1, and then someone (can't remember who) cherry picked it.
> My github repo
> is now behind my branch in the main repo.
>
> It would be nice to have my latest perlfaq updates cherrypicked into
> the maintenance branch though.
Which gets us back to what you said in your original post:
> The only question is who and when to pull the new versions into blead.
I think the who should be you and the when should be some intersection
of whenever you feel like it and whenever it seems like publishing an
update is worthwhile, such as when we're approaching a release. It
might be a little late to do another sync before 5.12.2, but in any
case I think it has to go into blead first.
> In article
> <AANLkTinkUqcz0-Hw4DH74FHy6cEUiNnznBQR07YacyyU@mail.gmail.com>, Craig
> A. Berry <craig.a.berry@gmail.com> wrote:
>
>> In that case should the following entry in perl5122delta.pod be
>> changed to reflect the newest new canonical location?
>>
>> =item *
>>
>> The version of L<perlfaq> shipped with the perl core has been updated to the
>> latest official FAQ version as available at
>> L<git://github.com/briandfoy/perlfaq.git>.
>
> Well, it should point to whereever you synced it from.
Actually I didn't sync anything, you did:
http://perl5.git.perl.org/perl.git/commitdiff/d12d61c
and then Merijn requested that it get pulled to maint, and a couple of
us voted +1, and then someone (can't remember who) cherry picked it.
> My github repo
> is now behind my branch in the main repo.
>
> It would be nice to have my latest perlfaq updates cherrypicked into
> the maintenance branch though.
Which gets us back to what you said in your original post:
> The only question is who and when to pull the new versions into blead.
I think the who should be you and the when should be some intersection
of whenever you feel like it and whenever it seems like publishing an
update is worthwhile, such as when we're approaching a release. It
might be a little late to do another sync before 5.12.2, but in any
case I think it has to go into blead first.