[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-inpu
From: |
Graham Percival |
Subject: |
Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input |
Date: |
Sun, 15 Nov 2009 03:07:21 +0000 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Sun, Nov 15, 2009 at 03:58:12AM +0100, Christian Herzberg wrote:
> Am Samstag, 14. November 2009 16:57:37 schrieb Graham Percival:
> > I'm very sorry! I forgot to mention that we don't use HTML
> > directly; we build the pages from the texinfo markup-language.
> > The source files for the website are in
> > Documentation/general/
>
> Let me say this in my words, to confirm that I understand this correct (May
> be
> this can give a clue, what level a section about changing the website could
> have. I have no pracise in git before):
>
> The source files for the website are in the git repository at
> http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=tree
> in the folder
> Documentation/general/
> the website I want to change is
> introduction.itexi
>
> I check it out with right-click on "raw" and "save file"
Correct.
(we are working on a gui to make this process easier, but it's not
ready yet)
> > Could you try only changing one or two things on the page, then
> > send me a patch for that? I'd like to check that the technical
> > side of things is working before you spend much time re-creating
> > your work.
>
> I will give it a try. You mean Patch as in Contributor's Guide, Section 1.3.1
> (Producing a patch)? Or could a simple output with "$ diff old new" fill your
> needs?
The info in CG 1.3.1 will only apply if you have checked out the
entire git tree. Simple output like "diff old new" is perfectly
fine for me*.
* note: some people want contributors to produce a patch with git,
since this adds more info (such as your name + email address), but
I don't think this is necessary. If you're familiar with diff,
then by all means use that tool.
I will be at a conference for the next few days, and might not
have internet access. If anybody else wants to view + commit any
patches from Christian, that would be nice; otherwise, I'll do it
when I return.
Cheers,
- Graham
- Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Chrisch, 2009/11/11
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Graham Percival, 2009/11/11
- Message not available
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Graham Percival, 2009/11/14
- Message not available
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input,
Graham Percival <=
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Werner LEMBERG, 2009/11/15
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Christian Herzberg, 2009/11/15
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Graham Percival, 2009/11/19
- Message not available
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Graham Percival, 2009/11/21
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Christian Herzberg, 2009/11/22
- Re: Hints for http://lilypond.org/doc/v2.13/Documentation/alternate-input, Graham Percival, 2009/11/22