Patrick McCarty wrote:
Okay, well at least it wasn't a problem with Git. Once in a great
while, I'm convinced that `git format-patch' creates malformed
patches. So from now on, I always apply my patches against a clean
master branch before submitting them.
I always assume I messed something u
2009/5/18 Jonathan Kulp :
> Good to hear. Do you have push access? If not, then would someone else
> mind pushing it for me? Thanks,
Happy to oblige. :)
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mail
On Mon, May 18, 2009 at 09:06:58AM -0500, Jonathan Kulp wrote:
> Patrick McCarty wrote:
>> On Sun, May 17, 2009 at 09:35:29PM -0500, Jonathan Kulp wrote:
>>> Patrick,
>>>
>>> I reset my git repo, re-did the changes, and made a new patch. A
>>> bunch of the changes are stripped whitespaces. I thin
Patrick McCarty wrote:
On Sun, May 17, 2009 at 09:35:29PM -0500, Jonathan Kulp wrote:
Patrick,
I reset my git repo, re-did the changes, and made a new patch. A
bunch of the changes are stripped whitespaces. I think I got all
the vim *.ily stuff in there this time, though. New patch attached.
On Sun, May 17, 2009 at 09:35:29PM -0500, Jonathan Kulp wrote:
> Patrick,
>
> I reset my git repo, re-did the changes, and made a new patch. A
> bunch of the changes are stripped whitespaces. I think I got all
> the vim *.ily stuff in there this time, though. New patch attached.
Great, it appl
Patrick,
I reset my git repo, re-did the changes, and made a new patch. A bunch of
the changes are stripped whitespaces. I think I got all the vim *.ily stuff
in there this time, though. New patch attached.
Jon
On Sun, May 17, 2009 at 6:48 PM, Jonathan Kulp wrote:
> Patrick McCarty wrote:
>
Patrick McCarty wrote:
Hmm. That's weird. I don't see the changes you made to
vim/lilypond-ftdetect.vim reflected in the patch.
If you run `git status', does it say that you have nothing to commit?
If not, then something might have went astray in the process of
amending the commit.
Here's
On Sun, May 17, 2009 at 05:04:18PM -0500, Jonathan Kulp wrote:
> On Sat, May 16, 2009 at 3:24 AM, Patrick McCarty wrote:
>
> > That's correct. At one point, I had filetype.vim in my ~/.vim
> > directory too, but since ftdetect/lilypond.vim does (basically) the
> > same thing, I've just been usin
On Sat, May 16, 2009 at 3:24 AM, Patrick McCarty wrote:
> That's correct. At one point, I had filetype.vim in my ~/.vim
> directory too, but since ftdetect/lilypond.vim does (basically) the
> same thing, I've just been using this file.
>
> > I've already made the change to lilypond-ftdetect.vim
On Sat, May 16, 2009 at 12:03:34AM -0500, Jonathan Kulp wrote:
> Patrick McCarty wrote:
>> On Fri, May 15, 2009 at 02:39:26PM -0500, Jonathan Kulp wrote:
>>> Here's a patch to add the .ily extension to the filetype.vim file in the
>>> sources and to the Application Usage 2.2.2 "Vim mode" sample fil
Patrick McCarty wrote:
On Fri, May 15, 2009 at 02:39:26PM -0500, Jonathan Kulp wrote:
Here's a patch to add the .ily extension to the filetype.vim file in the
sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
You should also add the *.ily to vim/lilypond-ftdetect.vim,
On Fri, May 15, 2009 at 02:39:26PM -0500, Jonathan Kulp wrote:
> Here's a patch to add the .ily extension to the filetype.vim file in the
> sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
You should also add the *.ily to vim/lilypond-ftdetect.vim, because
vim/filetype.vi
Here's a patch to add the .ily extension to the filetype.vim file in the
sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
From 2c173c2b6cacb37a7243585fb73ae81168aa40e8 Mon Sep 17 00:00:00 2001
From: Jonathan Kulp
Date: F
13 matches
Mail list logo
