Re: Hacking Perl (I think)

[ikegami]

in reply to Hacking Perl (I think)

You can get a snapshot of blead from http://perl5.git.perl.org/perl.git/snapshot/HEAD.tar.gz.

Although git patches are preferred, one created using diff -u should be acceptable too.

That said it'll be easier to use git, especially when it comes time to rebase your patches when you're about ready to submit them.

[Anonymous Monk]

Well... I really don't know how to use Git. And I guess I don't, really, no the purpose of Git. But if it is easier, I guess I should learn Git ;-)

[ikegami]

perlrepository tells you pretty much everything you need to know.

The git user manual is actually very good once you need something perlrepository doesn't cover.

[DrHyde]

The purpose of git is to be a version control system which you can use when you're offline. I'm told that it has some other funky features too, but I'm not convinced that they are either particularly important or couldn't be implemented with cvs or svn and a few shell scripts.

[ikegami]

That's besides the point of this conversation. The question isn't "Should I use a VCS?" or "Which VCS I should use?", but "How do I work work on Perl?" or "What would help me work on Perl?".

As someone who uses cvs, svn and git at work, I can assure you that there are definitely some advantages to git, and very few downsides. Some could indeed be supported by svn or cvs with proper tools, but then you'd have to spend your time writing those tools. Why would you want to spend your time porting git functionality to get *some* of the benefit of git?

Sorry, I've out of time, so I can't go into details. Catch me later.