From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Christian Feuersaenger <cfeuersaenger@users.sourceforge.net>
Subject: TikZ on the garden
Date: Wed, 12 Nov 2014 15:44:40 +0100 [thread overview]
Message-ID: <CALBOmsaWBGcCwt1MppK11B3LGDb3eGdSSD16s6zE-8jboUV8Kg@mail.gmail.com> (raw)
Hi,
What exactly should I to do with respect to TikZ on the garden (for
the minimals)?
Switch to the version of TikZ and pgfplots from TL 2014 + replace
t-tikz.tex with Hans' version and freeze in that state until TikZ is
fixed upstream?
Or just freeze at whatever version is in CVS at the moment and patch
t-tikz.tex and wait for the patch?
Any other/better suggestions?
And what version of pgfplots should I take?
Does anyone need the latest functionality of TikZ or pgfplots?
Ideally it would be nice if TikZ was fixed upstream, but developers
are currently busy and would like to understand patches before
applying them, so it might take a while before the code gets fixed. I
hate having to use CVS to go back in time (svn or git would be easier
to deal with; what date to use for CVS), but if that's the only option
...
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:[~2014-11-12 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 14:44 Mojca Miklavec [this message]
2014-11-12 14:55 ` luigi scarso
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=CALBOmsaWBGcCwt1MppK11B3LGDb3eGdSSD16s6zE-8jboUV8Kg@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=cfeuersaenger@users.sourceforge.net \
--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).