From: "Philipp A." <flying-sheep@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TikZ bug fixing (git, minimals, ...)
Date: Mon, 12 Sep 2011 17:14:05 +0200 [thread overview]
Message-ID: <CAN8d9g=4=CLzJDyGKwhh-kenn0cuhd7=_K8KCuw=B7MrhcBJkA@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsZoh=ccGwTixAEQZjLL6WayK-LURfa3FWSnn3AXweBn9w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1515 bytes --]
thanks for picking up my rant in such a constructive manner :)
A quick googling showed me this tool<http://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 more modern
version control system is inferring the most likely history given the
incomplete information that CVS records. cvs2svn has a long history of
making sense of even the most convoluted CVS repositories, and cvs2git uses
this same machinery. Therefore, cvs2git inherits the robustness and many of
the features of cvs2svn <http://cvs2svn.tigris.org/features.html>. cvs2svn
can convert just about every CVS repository we have ever seen, and includes
a plethora of options for customizing your conversion.
The output of cvs2git is one or more dump files that can be imported into
git using the excellent git
fast-import<http://www.kernel.org/pub/software/scm/git/docs/gitfast-import.html>tool.
Although cvs2git is considerably newer than cvs2svn, and much less well
tested, it is believed that cvs2git can (cautiously) be used for production
conversions. If you use cvs2git, please let us know how it worked for you!
~~~~
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.
hopefully,
philipp
[-- Attachment #1.2: Type: text/html, Size: 1621 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-09-12 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 9:51 Mojca Miklavec
2011-09-12 15:14 ` Philipp A. [this message]
2011-09-12 21:00 ` Mojca Miklavec
2011-09-12 21:37 ` Aditya Mahajan
2011-09-13 6:33 ` Mojca Miklavec
2011-09-14 9:08 ` Philipp A.
2011-09-14 10:38 ` Mojca Miklavec
2011-09-12 15:32 ` Aditya Mahajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN8d9g=4=CLzJDyGKwhh-kenn0cuhd7=_K8KCuw=B7MrhcBJkA@mail.gmail.com' \
--to=flying-sheep@web.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).