On 9/28/2012 2:52 AM, Volker Braun wrote:
I agree. Are you volunteering to write an "introduction to patching for
the impatient" tutorial? ;-)
"For the naive", I think. The impatient person's solution is to make
someone else do the work ;)
The patchbot already knows how to figure out patch
I agree. Are you volunteering to write an "introduction to patching for the
impatient" tutorial? ;-)
The patchbot already knows how to figure out patch dependencies, it would
be nice if there were a command "try out ths ticket" and it would pull in
all patches..
On Friday, September 28, 2012
On 9/27/2012 6:54 PM, Dima Pasechnik wrote:
Is there a "test" patch for Sage which doesn't do anything
substantive? I have been writing notes about how to patch a
Windows installation of Sage, and it would be nice to have an
example.
there should not be anything specific about patching Sage
On Tuesday, 25 September 2012 07:02:17 UTC+8, Ursula Whitcher wrote:
>
> On Monday, September 24, 2012 4:51:28 PM UTC-5, Volker Braun wrote:
>>
>> The VirtualBox guest additions are already installed in the VM that we
>> are distributing, but they don't do clipboard integration on the console
>
On Monday, September 24, 2012 4:51:28 PM UTC-5, Volker Braun wrote:
>
> The VirtualBox guest additions are already installed in the VM that we are
> distributing, but they don't do clipboard integration on the console (only
> in X).
>
> You can log in via ssh from the host machine, then you can u
The VirtualBox guest additions are already installed in the VM that we are
distributing, but they don't do clipboard integration on the console (only
in X).
You can log in via ssh from the host machine, then you can use the hosts'
terminal (which hopefully supports cut&paste):
ssh -p sage
