> I only posted an amended patch because Graham said he had reverted my
> first patch. Here's a patch against master.
Applied, pushed, thanks!
Jan
--
Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
_
On Tue, Dec 7, 2010 at 1:28 PM, Jan Nieuwenhuizen wrote:
> Let me think about that. What I would like is for Valentin
> to fix it the way he thinks it's best. Eg: two patches, one simple
> git revert --no-edit and the new patch. I don't like reverting other
> people's patches.
I only posted an
reverting is OK since the patch is wrong ad Valentin asks for it, right?
Let me think about that. What I would like is for Valentin
to fix it the way he thinks it's best. Eg: two patches, one simple
git revert --no-edit and the new patch. I don't like reverting other
people's patches.
Graham P
On Sat, Dec 4, 2010 at 6:37 PM, Valentin Villenave
wrote:
> Here's a new patch that you can use instead of the previous one.
> (Since you've reverted it.) Please let me know how that works!
Jan, where are we on this?
- do you want to officially git revert Valentin's previous patch, then
apply thi
On 12/4/10 1:32 PM, "Graham Percival" wrote:
> On Sat, Dec 4, 2010 at 6:37 PM, Valentin Villenave
> wrote:
>> On Sat, Dec 4, 2010 at 2:35 PM, Graham Percival
>> wrote:
>>> Since GUB master still cannot build lilypond due to that target_cpu
>>> error, I've reverted my local tree back to
>>>
Graham Percival writes:
> On Sat, Dec 4, 2010 at 6:37 PM, Valentin Villenave
> wrote:
>> On Sat, Dec 4, 2010 at 2:35 PM, Graham Percival
>> wrote:
>>> Since GUB master still cannot build lilypond due to that target_cpu
>>> error, I've reverted my local tree back to
>>> 2a8f076a015ac06b37a7f8
On Sat, Dec 4, 2010 at 6:37 PM, Valentin Villenave
wrote:
> On Sat, Dec 4, 2010 at 2:35 PM, Graham Percival
> wrote:
>> Since GUB master still cannot build lilypond due to that target_cpu
>> error, I've reverted my local tree back to
>> 2a8f076a015ac06b37a7f86537cf47691e65e745
>
> Here's a new
On Sat, Dec 4, 2010 at 2:35 PM, Graham Percival
wrote:
> Since GUB master still cannot build lilypond due to that target_cpu
> error, I've reverted my local tree back to
> 2a8f076a015ac06b37a7f86537cf47691e65e745
> which is the commit we used for 2.13.40.
Here's a new patch that you can use in
Since GUB master still cannot build lilypond due to that target_cpu
error, I've reverted my local tree back to
2a8f076a015ac06b37a7f86537cf47691e65e745
which is the commit we used for 2.13.40.
Carl, Neil, and Valentin have made great progress on the volleyball
regression bugs. I'm going to bo