#138: when we switch from svn.perl.org to trac, consider using git
----------------------+-----------------------------------------------------
Reporter: Infinoid | Owner:
Type: feature | Status: new
Priority: normal | Milestone:
Component: website | Version:
Severity: medium | Keywords: git svn trac plugin
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by Infinoid):
Replying to [comment:8 barney]:
> I haven't worked with git yet, but what I've heard and seen about git is
very convincing.
> My selfish reason for having Parrot code managed in Git, is that I want
to move Pipp
> to Github. I suppose that this would be easier when Parrot is already in
Git.
I don't know if this comment helps my request any, but... I don't think
changing parrot's SCM will affect your move much, either way.
Mark
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/138#comment:9>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
