Hello,
I noticed that running 'make' I get a message for flower/out/library.a
(as the make files are created).
--snip--
...
Making flower/out/file-path.o < cc
Making flower/out/library.a
ar: `u' modifier ignored since `D' is the default (see `U') < ***HERE***
ar: creating out/library.a
LGTM. I will hopefully run full builds soon again...
https://codereview.appspot.com/545270043/
Reviewers: lemzwerg, carl.d.sorensen_gmail.com, Dan Eble, thomasmorley651,
t.daniels_treda.co.uk, kieren_kierenmacmillan.info, c_sorensen, checkma,
Message:
Name has been changed to MeasureSpanner, and all references (including
file names) have been adjusted. Thanks for the reviews!
On Thu, Nov 21, 2019 at 9:45 AM Jonas Hahnfeld wrote:
>
> Am Donnerstag, den 21.11.2019, 16:30 +0100 schrieb Werner LEMBERG:
> > > Below is the console output. Any ideas?
> >
> >
> > Clone the repository anew, and everything should be fine again.
>
> This works of course but is pretty
David Kastrup writes:
> David Nalesnik writes:
>
>> Below is the console output. Any ideas?
>>
>> Thanks,
>> David
>>
>> [dev@lilydev:lilypond-git]$ git pull -r
>> error: cannot lock ref
>> 'refs/remotes/origin/dev/jmandereau/merge-make-and-stepmake':
>> 'refs/remotes/origin/dev/jmandereau'
David Nalesnik writes:
> Below is the console output. Any ideas?
>
> Thanks,
> David
>
> [dev@lilydev:lilypond-git]$ git pull -r
> error: cannot lock ref
> 'refs/remotes/origin/dev/jmandereau/merge-make-and-stepmake':
> 'refs/remotes/origin/dev/jmandereau' exists; cannot create
>
On Nov 21, 2019, at 10:30, Werner LEMBERG wrote:
> Clone the repository anew, and everything should be fine again.
>
> Don't forget to `transfer' your old local branches before deleting the
> old repository clone! I only had two local ones, so it was rather
> easy. But I guess some of you have
Am Donnerstag, den 21.11.2019, 16:30 +0100 schrieb Werner LEMBERG:
> > Below is the console output. Any ideas?
>
>
> Clone the repository anew, and everything should be fine again.
This works of course but is pretty destructive. A simple
$ git fetch --prune
did the job for me. This removes
> Below is the console output. Any ideas?
Clone the repository anew, and everything should be fine again.
It seems that git has been upgraded on Savannah; a comparison between
the old and the new clone shows a lot of differences in the `.git'
directory...
Maybe they forgot to set a
Oh. Me too.
:(
On Thu, 21 Nov 2019 15:07:30 +, David Nalesnik
wrote:
> Below is the console output. Any ideas?
>
> Thanks,
> David
>
> [dev@lilydev:lilypond-git]$ git pull -r
> error: cannot lock ref
> 'refs/remotes/origin/dev/jmandereau/merge-make-and-stepmake':
>
Below is the console output. Any ideas?
Thanks,
David
[dev@lilydev:lilypond-git]$ git pull -r
error: cannot lock ref
'refs/remotes/origin/dev/jmandereau/merge-make-and-stepmake':
'refs/remotes/origin/dev/jmandereau' exists; cannot create
Very nice.
I think there should be a changes.tely entry.
Carl
https://codereview.appspot.com/577130043/
Very nice.
I think there should be a changes.tely entry.
Carl
https://codereview.appspot.com/577130043/
I've added a comment about the docstring -- it's a request for
consideration, not a demand for change.
Also, I think a changes.tely entry should be included.
https://codereview.appspot.com/575330043/diff/551180043/scm/define-grob-properties.scm
File scm/define-grob-properties.scm (right):
Very nice, LGTM!
https://codereview.appspot.com/575330043/
LGTM
https://codereview.appspot.com/577130043/
16 matches
Mail list logo