Hi David,
On 2013-11-04, David Roe wrote:
> Even if you
> decide you don't want some code that you introduced, you should introduce a
> new commit that deletes the code rather than removing old commits and
> force-pushing your branch.
Good example.
So, what simple and easy-to-use command does g
I had updated my Xcode and OS system to 10.9 Mavericks in late October. I
was having no problems building and working with patches for a long time
until I touched some files that required certain certain libraries. When I
touched those files I was no longer able to complete 'sage -b'.
When
You can put "private" (not: secret) branches on trac, just don't link from
a ticket and you can do with them what you want. Or tell people in a
comment or in the ticket description that the branch is not ready for
public consumption. If you did that, then you can rewrite your history.
However,
On Monday, November 4, 2013 10:33:24 AM UTC-8, David Roe wrote:
>
> I agree with Volker: any plan which involves rewriting the history of your
> branch to make it "nicer" is a very bad idea. Once you push changes to
> trac, you really should not go back and rewrite your commits. Even if you
>
Relevant article by Linus Torvalds:
http://lwn.net/Articles/328438/
Best,
Gonzalo
On Mon, Nov 4, 2013 at 4:33 PM, David Roe wrote:
> I agree with Volker: any plan which involves rewriting the history of your
> branch to make it "nicer" is a very bad idea. Once you push changes to
> trac, you r
I agree with Volker: any plan which involves rewriting the history of your
branch to make it "nicer" is a very bad idea. Once you push changes to
trac, you really should not go back and rewrite your commits. Even if you
decide you don't want some code that you introduced, you should introduce a
n
Am 2013-11-04 17:56, schrieb Volker Braun:
> It means your patch increases the number of modules imported on startup.
> Try to use lazy_import if possible, and your own judgement if its not
> possible.
Thanks. I wasn't aware of lazy_import. I changed #15078 to use it.
Daniel
--
You received thi
Hi!
On 2013-11-04, kcrisman wrote:
> --=_Part_109_13671842.1383581913134
> Content-Type: text/plain; charset=ISO-8859-1
>
> I like this discussion, hopefully we'll find a good result. What if
> multiple people are contributing to a ticket - how might that play in for
> the various options?
It means your patch increases the number of modules imported on startup.
Try to use lazy_import if possible, and your own judgement if its not
possible.
On Monday, November 4, 2013 3:50:02 PM UTC, Daniel Krenn wrote:
>
> In http://trac.sagemath.org/ticket/15078 the patchbot says
> plugins.st
git blame already does cumulative blame over a range of commits. By mashing
commits together you don't gain anything. But you invalidate all branches
that were based on the un-mashed commits.
If you absolutely can't live with others noticing that you are human after
all, then you can still squ
I like this discussion, hopefully we'll find a good result. What if
multiple people are contributing to a ticket - how might that play in for
the various options?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group an
In http://trac.sagemath.org/ticket/15078 the patchbot says
plugins.startup_modules Failed
What does that mean or why is it failing?
Daniel
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
Dear Volker,
I will try not to import all from sage and import only those modules needed.
Thank you for support.
Pedro
On Saturday, November 2, 2013 7:23:25 PM UTC, Volker Braun wrote:
>
> You should never "from sage.all import *". For starters, that is already
> imported in the doctest framew
On Monday, November 4, 2013 7:15:19 AM UTC+1, Nils Bruin wrote:
>
> On Sunday, November 3, 2013 6:51:48 PM UTC-8, P Purkayastha wrote:
>
>> If you check out the branch locally, you can run a
>>
>> git diff
>>
>> to see the cumulative changes.
>>
>
> That's good to know. However, when trying
14 matches
Mail list logo
