As the developer, you should have nothing to do with Gitpan. It will (eventually) take care of itself as you make releases to CPAN. Do not make your dev repo a fork of the Gitpan repo.
Gitpan is not intended as a development repository. It's a reorganization of historical releases to make them available in a consistent manner across all distributions. The only time it has value to a developer is if you want to fill in gaps in the history of your development repository. Like if at some point in the past a new repo was started but the old repo was not imported, Gitpan can be used to fill in the old history so you have something.
Gitpan is not updating because the original import was done using a prototype that required a lot of babying to make it work. It had no logging and could very easily wedge itself. I started a rewrite but did not finish it. It's in the "rewrite" branch if anyone wants to work on it. Right now I have $work and Test::Builder2 sucking down my time.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||