#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 tene):

 +1 because the ability to use git directly instead of through git-svn
 would make my development experience more pleasant.

 possible -1 if this would cause problems for anyone or hinder anyone's
 progress.  This only applies if anyone can identify specific problems, and
 those problems are greater than the problems with svn.  It might be
 helpful to list the problems with svn?  I remember people complaining
 about merges, committing to tags, deleting all of the branches, merges,
 and metadata.  I haven't personally dealt with any of those, though.  All
 I know is that every time I have to touch SVN directly I break something,
 but that's probably better attributed to personal problems.

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/138#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to