On Mon, Nov 04, 2013 at 11:30:53PM -0800, Anne Schilling wrote:
> > With that in mind, I would aim for just using a bunch of branches in
> > the sage git repository, with a way to group those in collections that
> > would model our subcommunities: combinat / cluster_algebras /
> > categories / tableaux / crystals / dynamics / semigroups / ...
> > As Simon points out, some tags mechanism would be great for this.
>
> Talking to Andrew, tags are apparently not the right thing to do and are
> only used by release managers. On github we can just have various
> subdirectories for the various categories.
Let me raise a possible ambiguity: what I meant by ``tags'' is *some*
mechanism by which a single ticket/branch can be in several categories
at once; call it "keywords" if you prefer. I wasn't being specific
about whether we should be using "git's tags" for this or any other
mechanism. In any cases, subdirectories do not allow this feature
(unless we can have symbolic links???)
> > As Simon pointed out, this will be easy. However whether it's
> > practical or not will depend on how much time we will have to wait
> > for recompilation in average. Part of the answer will be in the
> > "compilation cache"[1] infrastructure that Andrew & co have been
> > exploring, but I don't know how far this project progressed.
>
> >From the sage-git version you can just do
>
> sage -f ccache
Excellent; thanks! Feedback about how it behaves in practice (speed,
space usage) is welcome!
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/groups/opt_out.
