In principle it could work for other projects, all it assumes is git and a
trac install with xmlrpc enabled and a few custom trac fields (namely
"Branch" and "Commit").
On Wednesday, May 28, 2014 6:57:04 AM UTC+1, Snark wrote:
>
> > https://github.com/sagemath/git-trac-command
> >
> > (It's
Hi,
(sorry if it's out-of-thread)
Le 28/05/2014 02:45, leif a écrit :
https://github.com/sagemath/git-trac-command
(It's IMHO a bit funny it's not included in Sage yet.)
I had seen it as optional package, but didn't pay much attention: is it
a generic git trac helper or a sage-specific one?
François Bissey wrote:
On Wed, 14 May 2014 06:57:53 Volker Braun wrote:
On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry
(sage-googlesucks@xxx) wrote:
In short, what is the git command to get a summary of the changes related
to a package
git log build/pkgs/
git trac find
Various comb
>
> If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
> they can review http://trac.sagemath.org/ticket/16299
I just reviewed it. Thanks for doing this, I recently ran into an annoying
memory leak in numpy 1.7.0, which was fixed in 1.7.1 (and 1.8.1).
Nathan
--
You re
On Wednesday, May 14, 2014 4:59:49 PM UTC+1, leif wrote:
>
> Volker Braun wrote:
> > git trac find
>
> Does that work for the changes/commits whose changelog entries we're
> about to delete?
>
Not sure I understand, but probably "yes". Given the sha1 of the commit
that deletes somethnig, you
Volker Braun wrote:
git trac find
Does that work for the changes/commits whose changelog entries we're
about to delete?
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
William Stein wrote:
On May 13, 2014 7:13 PM, "François Bissey"
mailto:francois.bis...@canterbury.ac.nz>> wrote:
> It has been more or less done progressively as we touch the various spkg
> rather than a big swipe. I guess someone could try to do it in an
automated
> way.
A one-liner, see be
Francois Bissey wrote:
Comments, especially about patches are still welcome. But a lot of stuff should
just go in the commit message.
"The" commit message, hopefully.
In short, what is the git command to get a summary of the changes related
to a package, with pointers to the related trac tic
Thierry wrote:
On Wed, May 14, 2014 at 01:43:24PM +1200, François Bissey wrote:
[...]
I know that the squashing of the changelog in the new style sage is
unpopular in some quarters but I am sticking to the official line.
I am not sure a hole in the documentation can serve as "the official
lin
François Bissey wrote:
The "official" line is the developer guide:
https://www.sagemath.org/doc/developer/packaging.html#the-spkg-txt-file
The only mention of the changelog is for old style spkg:
http://www.sagemath.org/doc/developer/packaging_old_spkgs.html#the-file-spkg-txt
Now, if you think t
10 matches
Mail list logo
