It seems the trac/git failure was not caused by the lack of space on /tmp
as it is still dysfunctional.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
The object is not on the git server (or not referenced by a branch).
$ git show 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
fatal: bad object 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
If you pushed something while the git repo was out of disk space then it
was NOT uploaded
On Thursday, May 21,
The object is not on the git server (or not referenced by a branch).
$ git show 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
fatal: bad object 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
If you pushed something while the git repo was out of disk space then it
was NOT uploaded
The point is
On Friday, May 22, 2015 at 6:13:28 PM UTC+2, kcrisman wrote:
http://git.sagemath.org/sage.git/diff/?id=75ab6f97a1bcf94a6fe4eb30d84dade96830b802
- related to http://trac.sagemath.org/ticket/1 and if you go up the
commit tree a little you see something about a temporary merge.
$
In case the one in charge was not aware, it seems the trac git interface
is half broken.
For instance,
http://git.sagemath.org/sage.git/diff/?id=2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
shows no diff.
I can confirm this - e.g.
