hi mojca, do you want to swich from cvs to git or just create a git mirror
of the cvs repo? in the latter case, i’d be interested in why you don’t
swich to git entirely.
2011/9/13 Mojca Miklavec mojca.miklavec.li...@gmail.com
When I tried to do conversion from CVS, the .cvsignore files are the
On Wed, Sep 14, 2011 at 11:08, Philipp A. wrote:
hi mojca, do you want to swich from cvs to git or just create a git mirror
of the cvs repo?
Create a git mirror.
in the latter case, i’d be interested in why you don’t
swich to git entirely.
Because I'm not the developer. That decision would
On Mon, Sep 12, 2011 at 17:14, Philipp A. wrote:
thanks for picking up my rant in such a constructive manner :)
A quick googling showed me this tool, cvs2git, whose “Development status”
section really sounds promising:
Development status
Most of the work of converting a repository
thanks for picking up my rant in such a constructive manner :)
A quick googling showed me this toolhttp://cvs2svn.tigris.org/cvs2git.html,
cvs2git, whose “Development status” section really sounds promising:
*Development status*
Most of the work of converting a repository from CVS to a
On Mon, 12 Sep 2011, Mojca Miklavec wrote:
We definitely need some ConTeXt specific bug tracking with automatic
email reminders for pgf developers to fix those bugs ;) ;) ;)
Another option is to rewrite all the code in $TEXMF/tex/context/pgf
directory in a more ConTeXtist way. Mainly this
On Mon, Sep 12, 2011 at 17:14, Philipp A. flying-sh...@web.de wrote:
thanks for picking up my rant in such a constructive manner :)
A quick googling showed me this tool, cvs2git, whose “Development status”
section really sounds promising:
Development status
Most of the work of
I hope this means that PGF/TikZ becomes hosted on Github – I think the team
there does a great job and the concept of “pull requests” really fits any
open source project, no matter how hard the criteria for patches are.
Sadly not. If I put their code to GitHub, this doesn't mean that
GitHub
