> You shouldn't worry about those files with question marks next to
> them. They won't prevent you from applying valid patches to the script
> repository.
I ended up having to add them, and then having to revert the png's,
before I could do anything. I don't use queues, though.
- kcrisman
--
Hi kcrisman,
On Sat, Dec 5, 2009 at 11:59 PM, kcrisman wrote:
> I still get
>
> ~/Desktop/sage-4.3.alpha1/sage -hg st
> ? hmac256
> ? jmol
> ? pilconvert.py
> ? pildriver.py
> ? pilfile.py
> ? pilfont.py
> ? pilprint.py
> ? sphinx-autogen
>
> And presumably this is what is not allowing me to do
>
I still get
~/Desktop/sage-4.3.alpha1/sage -hg st
? hmac256
? jmol
? pilconvert.py
? pildriver.py
? pilfile.py
? pilfont.py
? pilprint.py
? sphinx-autogen
And presumably this is what is not allowing me to do
hg_sage.import_patch. What do I do to get these files taken care of?
In hg_sage I think
On Dec 5, 7:29 am, Minh Nguyen wrote:
> Hi kcrisman,
>
> On Sat, Dec 5, 2009 at 11:09 PM, kcrisman wrote:
>
>
>
> > Forgive the question, but in a source build, I can neither commit
> > things here nor do I get a diff (I realize I am only using hg_sage.*,
> > so that might be the problem).
>
>
Hi kcrisman,
On Sat, Dec 5, 2009 at 11:09 PM, kcrisman wrote:
> Forgive the question, but in a source build, I can neither commit
> things here nor do I get a diff (I realize I am only using hg_sage.*,
> so that might be the problem).
The problem in question is located in the script repositor
On Dec 4, 5:24 am, Minh Nguyen wrote:
> Hi folks,
>
> When upgrading from Sage 4.3.alpha0 to 4.3.alpha1, I was asked to
> commit changes to the file sage-latest-online-package. I suspect this
> is due to executable bits of that file being either turned on or off.
Forgive the question, but in a
