From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Christian Feuersaenger <cfeuersaenger@googlemail.com>
Subject: TikZ bug fixing (git, minimals, ...)
Date: Mon, 12 Sep 2011 11:51:04 +0200 [thread overview]
Message-ID: <CALBOmsZoh=ccGwTixAEQZjLL6WayK-LURfa3FWSnn3AXweBn9w@mail.gmail.com> (raw)
(was: Latest betas break tikz matrix)
On Mon, Sep 12, 2011 at 11:16, Philipp A. wrote:
> Thank you both!
>
> We should get the TikZ devs to accept patches already. does anyone know
> anyone who has CVS access?
See
doc/generic/pgf/ChangeLog
Christian Feuersaenger ludewich, users.sourceforge.net
Christophe Jorssen cjorssen, users.sourceforge.net
Jannis Pohlmann jannis, xfce.org
Matthias Schulz ma.schulz, email.de
...
(Dear Christian: I'm still waiting for a fix for something that I sent
a while ago. This original thread "Latest betas break tikz matrix" is
at http://www.ntg.nl/pipermail/ntg-context/2011/thread.html.)
We definitely need some ConTeXt specific bug tracking with automatic
email reminders for pgf developers to fix those bugs ;) ;) ;)
In principle we could also create a git project, create a context
branch, apply the fixes to it and use that one in ConTeXt minimals,
hoping that PGF developers will pick them up. Now a question:
- It is trivial to convert CVS project into GIT project (git cvs import ...)
- It is trivial to rearrange the structure into TDS with a script (I
simply use a few rsync commands)
- I don't know how to combine both.
Does anyone have some nice idea how to take the existing CVS project
with complete history and make a TDS-compliang git project out of it
(keeping all the history, authors, ... etc.)
I also have commit rights for TeX Live, but I don't dare applying
patches without having them applied upstream. If nothing else, that
just postpones the problem to the time after PGF will release a new
version and that one won't work.
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
___________________________________________________________________________________
next reply other threads:[~2011-09-12 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 9:51 Mojca Miklavec [this message]
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.
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='CALBOmsZoh=ccGwTixAEQZjLL6WayK-LURfa3FWSnn3AXweBn9w@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.com \
--cc=cfeuersaenger@googlemail.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).