Dear Volker,
Le dimanche 23 septembre 2018 00:28:42 UTC+2, Volker Braun a écrit :
>
> Try "git remote prune origin" or "git remote update origin --prune"
>
Thanks ! this did it.
>
> Explanation: You only have a stale remote reference reference, this is
> slightly different from Dima's problem
Travis : "I'm sorry, but that really sounds like "I want to get really good
without practicing".
My hobby time credit is quite limited and there is a hugge difference
between "without practicing" and good dev time management inducing
*awareness* about the main Tools (or how to make good code
I assume that other research universities work about the same as at UC
Berkeley. Anyone can donate money to a professor's research activities
with a designation something like "to support Prof X's research in the
area of ABC". It is monitored by the university, but such "various donors"
funds are
Try "git remote prune origin" or "git remote update origin --prune"
Explanation: You only have a stale remote reference reference, this is
slightly different from Dima's problem who had the branch locally checked
out. The "git branch -d" only deletes local branches. You need to prune the
cached
Le samedi 22 septembre 2018 22:19:32 UTC+2, Erik Bray a écrit :
>
> Try
>
> $ git branch -d origin/u/embray/python3/sage-rings-polynomial-polydict
>
No such luck :
charpent@asus16-ec:/usr/local/sage-8$ git branch -d
origin/u/embray/python3/sage-rings-polynomial-polydict
error: branche 'origin/
Try
$ git branch -d origin/u/embray/python3/sage-rings-polynomial-polydict
You wouldn't have the above branch without "origin" unless you created a
remote tracking branch. It's only remote branches which you're having a
problem with
(note: this happened because I had an older branch named
u/embr
That's what this discussion and the wiki page are for, right? Are you
suggesting or asking for something else?
John
On Saturday, September 22, 2018 at 11:21:28 AM UTC-7, Dima Pasechnik wrote:
>
> IMHO it's better for a potential donor to see more info on how the
> money is spent, with the l
It doesn't seem to have hurt.
But it doesn't seem to have helped either : now I have two problematic
branches :
charpent@asus16-ec:/usr/local/sage-8$ git pull
remote: Counting objects: 99, done.
remote: Compressing objects: 100% (40/40), done.
remote: Total 40 (delta 29), reused 0 (delta 0)
Dépaq
I don't see why `git gc` would hurt it.
On Sat, 22 Sep 2018, 20:24 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:
> Okay. But this means I have to wait for this pruning...
>
> Unless you tell me it's a bad idea (and why), I'll try to git gc
> --agressive. At worst, Ill have to retr
Okay. But this means I have to wait for this pruning...
Unless you tell me it's a bad idea (and why), I'll try to git gc --agressive.
At worst, Ill have to retry from a fresh clone...
Le samedi 22 septembre 2018 21:19:59 UTC+2, Dima Pasechnik a écrit :
>
> IMHO it's the main tree that might use
IMHO it's the main tree that might use some pruning, as we now see the
second case of it being uncooperative
On Sat, 22 Sep 2018, 19:55 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:
> Should I try git gc (or possibly git gc aggressive) ?
> Wouldn't this make my tree potentiall
Should I try git gc (or possibly git gc aggressive) ?
Wouldn't this make my tree potentially unfit to future pushes ?
Le samedi 22 septembre 2018 20:27:08 UTC+2, Emmanuel Charpentier a écrit :
[ Snip... ]
--
You received this message because you are subscribed to the Google Groups
"sage-devel
On Sat, Sep 22, 2018 at 11:21 AM, Dima Pasechnik wrote:
> IMHO it's better for a potential donor to see more info on how the
> money is spent, with the list of events/tasks on what the donations
> are spent. An Sage project outsider won't have a clue, and might have
> a feeling it goes into a sink
Le samedi 22 septembre 2018 20:35:23 UTC+2, Dima Pasechnik a écrit :
>
> And, by the way, what is the remote you are pulling from?
>
>From my .git/config file :
[remote "origin"]
url = g...@git.sagemath.org:sage.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remo
Le samedi 22 septembre 2018 20:33:23 UTC+2, Dima Pasechnik a écrit :
>
> On Sat, Sep 22, 2018 at 7:27 PM Emmanuel Charpentier
> > wrote:
> >
> > Thanks, Dimitri !
> >
> > But I'm not out of the woods : I do not know how to delete this branch.
> Git tells me it doesn't know about it :
> >
And, by the way, what is the remote you are pulling from?
On Sat, Sep 22, 2018 at 7:33 PM Dima Pasechnik wrote:
>
> On Sat, Sep 22, 2018 at 7:27 PM Emmanuel Charpentier
> wrote:
> >
> > Thanks, Dimitri !
> >
> > But I'm not out of the woods : I do not know how to delete this branch. Git
> > tell
On Sat, Sep 22, 2018 at 7:27 PM Emmanuel Charpentier
wrote:
>
> Thanks, Dimitri !
>
> But I'm not out of the woods : I do not know how to delete this branch. Git
> tells me it doesn't know about it :
>
> charpent@asus16-ec:/usr/local/sage-8$ git branch -d
> u/embray/python3/sage-rings-polynomial
Thanks, Dimitri !
But I'm not out of the woods : I do not know how to delete this branch. Git
tells me it doesn't know about it :
charpent@asus16-ec:/usr/local/sage-8$ git branch -d
u/embray/python3/sage-rings-polynomial-polydict
error: branche 'u/embray/python3/sage-rings-polynomial-polydict'
IMHO it's better for a potential donor to see more info on how the
money is spent, with the list of events/tasks on what the donations
are spent. An Sage project outsider won't have a clue, and might have
a feeling it goes into a sinkhole rather than into well-specified
meaningful activities.
On Sa
On Sat, Sep 22, 2018 at 7:10 PM Dima Pasechnik wrote:
>
> You are not the one hit by this particular branch of our vast git tree. See
"the one" -> "the only one"
> https://trac.sagemath.org/ticket/24762#comment:15
> and the following comments.
>
>
>
> On Sat, 22 Sep 2018, 18:53 Emmanuel Charpent
You are not the one hit by this particular branch of our vast git tree. See
https://trac.sagemath.org/ticket/24762#comment:15
and the following comments.
On Sat, 22 Sep 2018, 18:53 Emmanuel Charpentier, <
emanuel.charpent...@gmail.com> wrote:
> I wanted to update my (current) sage 8.4-beta4 to
I wanted to update my (current) sage 8.4-beta4 to beta6
Fetch works okay. Then :
charpent@asus16-ec:/usr/local/sage-8$ git status
Sur la branche develop
Votre branche est en retard sur 'origin/develop' de 652 commits, et peut
être mise à jour en avance rapide.
(utilisez "git pull" pour mettre
On Saturday, September 22, 2018 at 7:36:52 AM UTC-7, William wrote:
>
> On Sat, Sep 22, 2018 at 3:45 AM, Dima Pasechnik > wrote:
> > On Sat, Sep 22, 2018 at 11:21 AM Volker Braun > wrote:
> >>
> >> Afair the Sage foundation is a US non-profit with the necessary
> accounting busywork graciou
On Sat, Sep 22, 2018 at 3:45 AM, Dima Pasechnik wrote:
> On Sat, Sep 22, 2018 at 11:21 AM Volker Braun wrote:
>>
>> Afair the Sage foundation is a US non-profit with the necessary accounting
>> busywork graciously provided by UW; So I'm sure there is similar reporting
>> thats either published
On Sat, Sep 22, 2018 at 11:21 AM Volker Braun wrote:
>
> Afair the Sage foundation is a US non-profit with the necessary accounting
> busywork graciously provided by UW; So I'm sure there is similar reporting
> thats either published or available to the public.
> Though I've never read the Ober
Afair the Sage foundation is a US non-profit with the necessary accounting
busywork graciously provided by UW; So I'm sure there is similar reporting
thats either published or available to the public. Though I've never read
the Oberwolfach financial report ;-)
On Friday, September 21, 2018 at
On Friday, September 21, 2018 at 2:43:32 PM UTC+2, Thierry
(sage-googlesucks@xxx) wrote:
>
> Agreed. But how should we deal with testing networkx ?
Print a warning that nose is required and skip
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
27 matches
Mail list logo
