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: Wed, 14 Sep 2011 11:08:17 +0200 [thread overview]
Message-ID: <CAN8d9gk19FCbGJpimEhwwUB7K2=xO0WxkAt=_9DFUZKLX4m5AQ@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsY_N+nHB4oxY15g-isXH9_P+uYfyqUsn3WVycstTEPyYA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1420 bytes --]
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.lists@gmail.com>
> 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.
>
that cvs2git didn’t build it in makes me wonder what the big problem is.
both use shell-style wildcards, both can be anywhere in the path and apply
to that subpath, so there must be some hidden caveat…
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.
>
yes, there is such a thing. it is aptly named “pre-commit hook”:
http://book.git-scm.com/5_git_hooks.html
but since there are many settings in git (e.g. core.autocrlf for line
endings), i’d guess there are some for encoding, too. i might be mistaken,
though.
Mojca
>
philipp
[-- Attachment #1.2: Type: text/html, Size: 2110 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-14 9:08 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
2011-09-14 9:08 ` Philipp A. [this message]
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='CAN8d9gk19FCbGJpimEhwwUB7K2=xO0WxkAt=_9DFUZKLX4m5AQ@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).