ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TikZ bug fixing (git, minimals, ...)
Date: Tue, 13 Sep 2011 08:33:26 +0200	[thread overview]
Message-ID: <CALBOmsY_N+nHB4oxY15g-isXH9_P+uYfyqUsn3WVycstTEPyYA@mail.gmail.com> (raw)
In-Reply-To: <CAN8d9g=4=CLzJDyGKwhh-kenn0cuhd7=_K8KCuw=B7MrhcBJkA@mail.gmail.com>

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 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. 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 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 took a look at their webpage after reading that cvs2svn is capable
of converting .cvsignore into svn properties.

When I tried to do conversion from CVS, the .cvsignore files are the
only leftovers that somehow bother me (I would really like to get rid
of .cvsignore files and put some gitignore somewhere, without my
commit being visible), but then I noticed that .cvsignore ->
.gitignore conversion is still on TODO list.

The other thing that would make me happy would be the ability to apply
some hook to do some transformation of code before comitting to git
(let's say that I would want to reencode files into UTF-8 or that I
would want to move or rename some files before the actual commit). If
you know a simple way to do this, please let me know.

Mojca


Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2011-09-13  6:33 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.
2011-09-12 21:00   ` Mojca Miklavec
2011-09-12 21:37     ` Aditya Mahajan
2011-09-13  6:33   ` Mojca Miklavec [this message]
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=CALBOmsY_N+nHB4oxY15g-isXH9_P+uYfyqUsn3WVycstTEPyYA@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).