On 2016-06-06 17:48, Dima Pasechnik wrote:
I don't know how to create a working repo from .git/ alone...
Just checkout something and then "git reset --hard" works.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group a
On Monday, June 6, 2016 at 4:13:43 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-06-06 16:44, Dima Pasechnik wrote:
> > And put it somewhere public, e.g. on github.
>
> I have simply tarred up my .git directory at
>
> http://sage.ugent.be/www/jdemeyer/sagetrac-git.tar.bz2
>
I copied it to GCE
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
I have simply tarred up my .git directory at
http://sage.ugent.be/www/jdemeyer/sagetrac-git.tar.bz2
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsu
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
I don't think I can push 6930 branches to github. After a while, I get
this error:
error: failed to push some refs to 'https://github.com/jdemeyer/sage.git'
error: git-remote-https died of signal 13
--
Y
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
git fetch trac --all
(or perhaps even just 'git fetch trac' would have produced a full backup)
I did "git fetch trac" after the Sage 7.3.beta3 upgrade, so very recently.
--
You received this message becaus
And put it somewhere public, e.g. on github.
git fetch trac --all
(or perhaps even just 'git fetch trac' would have produced a full backup)
(please excuse my ignorance, I don't know how to make such a recovery repo
quickly - but first we need to find the data...)
Dima
--
You received this me
