On Tue Jul 16 06:49:23 2013, ANDREMAR wrote:
Show quoted text> Could you put that dump of the svn repo online somewhere? I could take
> a crack at converting the repos there as well if you want. We have
> converted a lot of repos at work (including things like splitting
> one svn repo into many git repos).
>
> How important are the "difficult" things, like branches, and tags? I
> assume tags are more important, but I don't know the state of the
> branches
Branches I know myself to have committed:
* rt64929 - This was for the ticket of the same number, which was about having ProhibitUnusedVariables find more unused variables. The work bogged down with concerns about false positives. The code has been released as a separate distribution, Perl-Critic-Policy-Variables-ProhibitUnusedVarsStricter, the branch deleted, and the ticket closed.
* rt38289 - This was for the ticket of the same number, which called for a policy flagging capture variables in subroutine arguments. I have no idea of the state of this code, though I know it was never merged into the core. If this would be better as a separate policy please let me know, though I can't commit to getting it quickly.
* violation_named_args - Work to convert violation creation from positional argumnents to named arguments. The aim was to be able to override the line and column numbers calculated from the PPI object (e.g. to provide a better idea where the error was in a large block of POD). This was abandoned because of concerns over where to put the '## no critic' if the error was to be suppressed. It can probably be deleted.
Unfortunately there are a lot of other things going on in my life right now, not all of them things I would wish for. What time I have had for Perl has been largely consumed by Astro::SpaceTrack (U. S. Strat Com changed the API, and the old one retired today). I know excuses are not what Perl::Critic needs right now. I will do what I can.
Tom