Hi Jan,
On Wed, Feb 18, 2009 at 09:00:50AM +, Jan Nieuwenhuizen wrote:
>
> Ah, well that's totally bogus. It should be filled by this command
> in libtools' configure
>
> mingw* | cegcc*)
> # MinGW DLLs use traditional 'lib' prefix
> soname_spec='${libname}`echo ${release} |
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> Johannes Schindelin wrote:
> > Hi,
> >
> > On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> >
> > > I realized after I sent it, though, that I sent it from my Thunderbird
> > > email client and this historically has jacked up the line endings.
> >
> J
Johannes Schindelin wrote:
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
I realized after I sent it, though, that I sent it from my Thunderbird
email client and this historically has jacked up the line endings.
Johannes,
If you still have the email with my patch attached, could you open it
Johannes Schindelin wrote:
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
I realized after I sent it, though, that I sent it from my Thunderbird
email client and this historically has jacked up the line endings.
We had a very "interesting" discussion with one of the Thunderbirds on the
Git l
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> I realized after I sent it, though, that I sent it from my Thunderbird
> email client and this historically has jacked up the line endings.
We had a very "interesting" discussion with one of the Thunderbirds on the
Git list (who I dragged into th
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> Again, Johannes, many thanks for your patience in explaining this to a
> non-developer. :)
You are very welcome!
Thank you for your contributions,
Dscho
___
lilypond-devel mailing list
lilypond-devel@
Carl D. Sorensen wrote:
Jon,
Now that you've got git installed, you can do this much easier.
I've had git installed for a long time I just didn't know any commands
except git pull origin. :)
8. send patch to someone with commit privileges
Keep doing this.
Just now I sent a patch
Graham Percival wrote Wednesday, February 18, 2009 2:33 PM
On Wed, Feb 18, 2009 at 08:18:09AM -0600, Jonathan Kulp wrote:
Graham Percival wrote:
For shame! Have you forgotten about the @qq{} macro?! ;P
Hey! I see a spot right above mine where somebody else forgot
@qq{}
Ok, point for
Ok I found a typo in the git instructions of CG and followed your
instructions to create the patch using git. Seems to have worked great!
Would someone with push privileges please review the patch and apply if
it looks ok?
Again, Johannes, many thanks for your patience in explaining this to a
On 2/18/09 9:49 AM, "Jonathan Kulp" wrote:
>
> I don't have commit privileges. Is this commit command a local commit
> or...where does it commit to? Frankly I'm scared of committment. :) I
> also don't understand which files it's comparing. When you decide to
> edit a file, do you work dir
Hi,
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> Johannes Schindelin wrote:
>
> > On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> >
> > > Am I correct in thinking that [git format-patch] creates the patch
> > > by comparing my local (changed) file with the corresponding file in
> > > the remote gi
Johannes Schindelin wrote:
Hi.
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
Am I correct in thinking that [git format-patch] creates the patch by
comparing my local (changed) file with the corresponding file in the
remote git repository?
No, it creates patches from commits. So you use Git as
On wo, 2009-02-18 at 14:55 +0100, Jan Nieuwenhuizen wrote:
Hi John,
> How hard is it for you to install another python and try that?
> Does fedora carry python2.4 or python2.6 (or even python3) packages
> that you can install alongside your 2.5.1, for example.
Just to be sure we're not chasing
Hi,
On Wed, 18 Feb 2009, Graham Percival wrote:
> On Wed, Feb 18, 2009 at 03:57:39PM +0100, Johannes Schindelin wrote:
> > Hi.
> >
> > On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> >
> > > Am I correct in thinking that [git format-patch] creates the patch by
> > > comparing my local (changed) f
On Wed, Feb 18, 2009 at 03:57:39PM +0100, Johannes Schindelin wrote:
> Hi.
>
> On Wed, 18 Feb 2009, Jonathan Kulp wrote:
>
> > Am I correct in thinking that [git format-patch] creates the patch by
> > comparing my local (changed) file with the corresponding file in the
> > remote git repositor
Hi.
On Wed, 18 Feb 2009, Jonathan Kulp wrote:
> Am I correct in thinking that [git format-patch] creates the patch by
> comparing my local (changed) file with the corresponding file in the
> remote git repository?
No, it creates patches from commits. So you use Git as usual:
(inspec
Graham Percival wrote:
On Tue, Feb 17, 2009 at 05:54:24PM +0100, Johannes Schindelin wrote:
Hi,
On Tue, 17 Feb 2009, Jonathan Kulp wrote:
Yes, it does set things up properly. I first acquired the repo using
the git-clone command and now I grab updates just fine with git pull
origin. I thin
On Wed, Feb 18, 2009 at 03:25:59PM +0100, Johannes Schindelin wrote:
>
> Sorry, I was _way_ too terse (but look at the time I wrote this; and I was
> still working, not watching TV)...
:)
> What I really meant is: A 'git clone' will fetch too many branches. So it
> is not efficient. But it i
On Wed, Feb 18, 2009 at 08:18:09AM -0600, Jonathan Kulp wrote:
> Graham Percival wrote:
>> For shame! Have you forgotten about the @qq{} macro?! ;P
>>
>
> Hey! I see a spot right above mine where somebody else forgot @qq{}
Ok, point for you. :P
> 5.2 the word "docs" is in straight quotes. S
Hi,
On Wed, 18 Feb 2009, Graham Percival wrote:
> On Tue, Feb 17, 2009 at 05:53:06PM +0100, Johannes Schindelin wrote:
> >
> > > 1. git-clone gets the entire repo, not just the particular
> > > branch that you want.
> >
> > Indeed, but as Git is pretty efficient, simplicity beats correctness
Graham Percival wrote:
For shame! Have you forgotten about the @qq{} macro?! ;P
Cheers,
- Graham
Hey! I see a spot right above mine where somebody else forgot @qq{}--in
5.2 the word "docs" is in straight quotes. Should I make a patch or
is this one supposed to have straight quotes?
J
On Tue, Feb 17, 2009 at 05:53:06PM +0100, Johannes Schindelin wrote:
>
> > 1. git-clone gets the entire repo, not just the particular
> > branch that you want.
>
> Indeed, but as Git is pretty efficient, simplicity beats correctness here.
What if a newbie wants to fix some typos in the English
On Wed, Feb 18, 2009 at 08:07:17AM -0600, Jonathan Kulp wrote:
> Trevor Daniels wrote:
>>
>>> For shame! Have you forgotten about the @qq{} macro?! ;P
>
> No, I haven't forgotten it at all. I never even heard of it! Is this
> what you use instead of "whatever you want in quotes"? So it would
Trevor Daniels wrote:
Graham, you wrote Wednesday, February 18, 2009 1:17 PM
For shame! Have you forgotten about the @qq{} macro?! ;P
No, I haven't forgotten it at all. I never even heard of it! Is this
what you use instead of "whatever you want in quotes"? So it would be
@qq{whatever
On wo, 2009-02-18 at 11:48 +0100, John Mandereau wrote:
> After a successful bootstraping stage, I tried "make -f lilypond.make"
> and "make -f lilypond.make installers"; both failed with the attached log.
Weird. Dependencies seem to be failing utterly. But how? Han-Wen,
any great ideas?
> I
On wo, 2009-02-18 at 11:41 +0100, John Mandereau wrote:
Hi John,
> I needed the attached patch (error log attached too) to succesfully
> complete "make -f lilypond.make bootstrap".
Thanks, applied. It puzzles me that on darwin libiberty is installed
in lib64...
Jan.
--
Jan Nieuwenhuizen | G
Graham, you wrote Wednesday, February 18, 2009 1:17 PM
For shame! Have you forgotten about the @qq{} macro?! ;P
I fixed this before pushing it, so it's OK in git.
Trevor
On Mon, Feb 16, 2009 at 01:01:55PM -0600, Jonathan Kulp wrote:
Here's a patch for the FIXME DOING SOMETHING part.
J
On Tue, Feb 17, 2009 at 05:54:24PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 17 Feb 2009, Jonathan Kulp wrote:
>
> > Yes, it does set things up properly. I first acquired the repo using
> > the git-clone command and now I grab updates just fine with git pull
> > origin. I think thes
For shame! Have you forgotten about the @qq{} macro?! ;P
Cheers,
- Graham
On Mon, Feb 16, 2009 at 01:01:55PM -0600, Jonathan Kulp wrote:
> Here's a patch for the FIXME DOING SOMETHING part.
>
> Jon
>
> On Sun, Feb 15, 2009 at 4:34 PM, Valentin Villenave
> wrote:
>
> 2009/2/15 Graham Pe
After a successful bootstraping stage, I tried "make -f lilypond.make"
and "make -f lilypond.make installers"; both failed with the attached log.
In bootstraping, Flex and Guile are built for target "tools", which I
find strange, whereas they are not built for each target platform. I
also mis
Hi Jan,
Jan Nieuwenhuizen a écrit :
Ah, you reported something like this before... A fixlet for this is in
HEAD (full rebuild ahead).
I needed the attached patch (error log attached too) to succesfully
complete "make -f lilypond.make bootstrap".
John
>From ad674166ea290a28a6865d576088fcdcc
On di, 2009-02-17 at 23:10 -0300, Han-Wen Nienhuys wrote:
> Working platforms: linux-x86, mingw, linux-ppc, linux-64,
> freebsd-x86, darwin-x86, darwin-ppc.
>
> Still failing: freebsd-64:
Great! Just fyi, with GUB3 HEAD, freebsd-64 still builds for me
http://lilypond.org/~janneke/freebsd-6
On di, 2009-02-17 at 10:40 -0800, Patrick McCarty wrote:
Hi Patrick,
> # Compile-time system search path for libraries.
> sys_lib_search_path_spec=" =./i686-pc-linux-gnu/4.3.3/ ./
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/ /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.
On di, 2009-02-17 at 13:55 -0800, Patrick McCarty wrote:
Hi Patrick,
> With the latest HEAD, gmp fails at configure for both darwin-x86 and
> darwin-ppc. The ppc build was successful for me before your last
> commit "Do not set ABI ...".
Okay, reverted. Together with Han-Wen's
2852b2e...
34 matches
Mail list logo
