> > IMO, a better practice is to merge in old branches to a branch based off
> > develop. If you want to rebase, then run rebase. That way you never have
> > old cruft and have to watch Sage do a massive rebuild of things with
> only
> > changed timestamps. For example
> >
> > $ git checkou
I have the same problem :
charpent@p-202-021:/usr/local/sage-8$ git status
Sur la branche 8_1_R_343
Fichiers non suivis:
(utilisez "git add ..." pour inclure dans ce qui sera validé)
src/sage/libs/cypari2/
aucune modification ajoutée à la validation mais des fichiers non suivis
sont présents
On Saturday, December 9, 2017 at 5:10:51 AM UTC+9, Simon King wrote:
>
> Hi Travis,
>
> On 2017-12-07, Travis Scrimshaw > wrote:
> > IMO, a better practice is to merge in old branches to a branch based off
> > develop. If you want to rebase, then run rebase. That way you never have
> > old cr
Hi Travis,
On 2017-12-07, Travis Scrimshaw wrote:
> IMO, a better practice is to merge in old branches to a branch based off
> develop. If you want to rebase, then run rebase. That way you never have
> old cruft and have to watch Sage do a massive rebuild of things with only
> changed timestam
On Friday, December 8, 2017 at 8:30:48 AM UTC+9, Travis Scrimshaw wrote:
>
>
>
>> Anyway. The branch used to be an old one. I checked it out and then
>> rebased on top of the latest develop. Do I understand correctly that
>> while rebasing, git failed to remove the cypari2 folder?
>>
>> IMO, a
>
> Anyway. The branch used to be an old one. I checked it out and then
> rebased on top of the latest develop. Do I understand correctly that
> while rebasing, git failed to remove the cypari2 folder?
>
> IMO, a better practice is to merge in old branches to a branch based off
develop. If yo
On 2017-12-07, François Bissey wrote:
> Seems like it. Which is why I asked if there was anything in it.
I think it was empty before I removed it.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
> On 8/12/2017, at 11:48, Simon King wrote:
>
> Hi François,
>
> On 2017-12-07, François Bissey wrote:
>>> Strangely, git status mentions
>>> src/sage/libs/cypari2/
>>> which my local branch is *not* touching. So, what's happening?
>>>
>>
>> Anything in that folder? That folder has been r
Hi François,
On 2017-12-07, François Bissey wrote:
>> Strangely, git status mentions
>>src/sage/libs/cypari2/
>> which my local branch is *not* touching. So, what's happening?
>>
>
> Anything in that folder? That folder has been removed when cypari2 has been
> made a separate package. git s
> On 8/12/2017, at 11:12, Simon King wrote:
>
> On 2017-12-07, Simon King wrote:
>> Hi!
>>
>> Building Sage again, I get the error
>> InternalError: Internal compiler error: 'cysignals/signals.pxi' not
>> found
>>
>> Unfortunately, the error did not go away after "make distclean".
>>
>> W
On 2017-12-07, Simon King wrote:
> Hi!
>
> Building Sage again, I get the error
> InternalError: Internal compiler error: 'cysignals/signals.pxi' not
> found
>
> Unfortunately, the error did not go away after "make distclean".
>
> What can I do? The error occurs on some local branch (different
11 matches
Mail list logo
