Can anyone see a reason why we have a config step (init::headers) to
generate this list of files? Looks like it's just grepping through
the MANIFEST to find them -
They are then thrown on the "big pile" of headers in GENERAL_H_FILES,
and (incorrectly) in the PMC dependencies. Even if they were us
Me and Matt have been unable to generate coverage reports, so I had a
look at the make cover targets. The actual problem were changes and a
regression in recent Devel::Cover versions, but there turned out to be
some more problems.
See branch nwellnhof/make_cover
Changes:
* Run gcov from buil
Howdy,
> Someone would still have to update the github repo with the docs.
Nope, it could be a git hook and fully automated.
Duke
--
Jonathan "Duke" Leto
jonat...@leto.net
http://leto.net
___
http://lists.parrot.org/mailman/listinfo/parrot-dev
On Mon, Dec 27, 2010 at 12:17 PM, Andrew Whitworth
wrote:
> On Mon, Dec 27, 2010 at 11:21 AM, Will Coleda wrote:
>> (An alternative approach would
>> be to just put the website in a github repo and just have it do an
>> update every day or so.)
>
> In the long term I feel like this is probably th
Howdy Prabu,
Thanks for letting us know the fix! That should be in our
documentation somewhere.
Duke
On Sun, Dec 26, 2010 at 10:07 PM, Prabu wrote:
> Hi,
> I got the answer.
> I just want to use "--encoding=utf8" when running the installable_mylang.
>
> Regards
> Prabu
> (google profile)
>
>
>
On Mon, Dec 27, 2010 at 11:21 AM, Will Coleda wrote:
> (An alternative approach would
> be to just put the website in a github repo and just have it do an
> update every day or so.)
In the long term I feel like this is probably the best way to go.
Moving certain documentation (the book, etc) out
On Thu, Dec 23, 2010 at 5:17 PM, Jonathan Leto wrote:
> Howdy,
>
> Could someone update docs.parrot.org to use the latest release?
Done; added 2.10.0, 2.10.1, and 2.11.0, all of which were skipped by
their respective release managers.
$ ls -l | egrep '(devel|latest|stable|supported)'|cut -c 45-
