Re: [sage-devel] Re: Checking out old branches

2016-11-22 Thread Robert Bradshaw
On Sat, Nov 19, 2016 at 12:40 AM, Jeroen Demeyer wrote: > On 2016-11-18 20:48, Robert Bradshaw wrote: >> >> Hopefully with a good ccache/cycache rebuilding from a fresh clone >> should be fast too. > > > Speaking of cycache, is there any chance that the following will be fixed > some day? > > http

Re: [sage-devel] Re: Checking out old branches

2016-11-19 Thread Jeroen Demeyer
On 2016-11-18 20:48, Robert Bradshaw wrote: Hopefully with a good ccache/cycache rebuilding from a fresh clone should be fast too. Speaking of cycache, is there any chance that the following will be fixed some day? https://github.com/cython/cython/issues/1393 https://github.com/cython/cython

Re: [sage-devel] Re: Checking out old branches

2016-11-18 Thread Robert Bradshaw
On Fri, Nov 18, 2016 at 12:39 AM, David Roe wrote: > > On Fri, Nov 18, 2016 at 2:45 AM, Volker Braun wrote: >> >> On Friday, November 18, 2016 at 8:12:32 AM UTC+1, David Roe wrote: >>> >>> Create a new git trac subcommand to replace `git trac checkout 1234`, say >>> `git trac old 1234`. This wou

Re: [sage-devel] Re: Checking out old branches

2016-11-18 Thread Clemens Heuberger
On 2016-11-18 10:05, David Roe wrote: > > > On Fri, Nov 18, 2016 at 3:49 AM, Volker Braun > wrote: > > The .git dir doesn't have to be in the working tree: > > git --git-dir= --work-tree= > > But I think its very confusing to have another working tree

[sage-devel] Re: Checking out old branches

2016-11-18 Thread David Roe
On Fri, Nov 18, 2016 at 3:49 AM, Volker Braun wrote: > The .git dir doesn't have to be in the working tree: > > git --git-dir= --work-tree= > > But I think its very confusing to have another working tree inside the > working tree, thats rather confusing and error prone. E.g. what does "git > comm

[sage-devel] Re: Checking out old branches

2016-11-18 Thread Volker Braun
The .git dir doesn't have to be in the working tree: git --git-dir= --work-tree= But I think its very confusing to have another working tree inside the working tree, thats rather confusing and error prone. E.g. what does "git commit" do in that situation? IMHO its conceptually much easier to ju

[sage-devel] Re: Checking out old branches

2016-11-18 Thread David Roe
On Fri, Nov 18, 2016 at 2:45 AM, Volker Braun wrote: > On Friday, November 18, 2016 at 8:12:32 AM UTC+1, David Roe wrote: >> >> Create a new git trac subcommand to replace `git trac checkout 1234`, say >> `git trac old 1234`. This would fetch the branch, check it out into a >> completely separat

[sage-devel] Re: Checking out old branches

2016-11-17 Thread Volker Braun
On Friday, November 18, 2016 at 8:12:32 AM UTC+1, David Roe wrote: > > Create a new git trac subcommand to replace `git trac checkout 1234`, say > `git trac old 1234`. This would fetch the branch, check it out into a > completely separate folder within ($SAGE_ROOT/merge_tree or something), > me

[sage-devel] Re: Checking out old branches

2016-11-17 Thread Jean-Pierre Flori
On Friday, November 18, 2016 at 8:12:32 AM UTC+1, David Roe wrote: > > If I checkout an old branch (say, from one or two versions of Sage ago), > it essentially forces a rebuild of all of Sage, even if I think better of > it and checkout develop immediately. The rebuild is a consequence of the