git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Wincent Colaiuta <win@wincent.com>
Cc: Sergei Organov <osv@javad.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Documentation: fix git-clone manpage not to refer to itself
Date: Tue, 20 Nov 2007 11:28:11 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711201126430.27959@racer.site> (raw)
In-Reply-To: <3FC9A391-AED0-4988-B1F7-EE5C06AD1137@wincent.com>

Hi,

On Tue, 20 Nov 2007, Wincent Colaiuta wrote:

> El 19/11/2007, a las 14:35, Johannes Schindelin escribi?:
> 
> > - it makes writing the perl script to do a very tiny subset of 
> > asciidoc formatting much harder.  We encounter enough problems with 
> > the different versions of asciidoc/docbook combinations that I think 
> > this perl script would be actually useful.
> > 
> > I know that the user manual uses some advanced features, too, but it 
> > did not use ifdef in the main text, for example, let alone nested 
> > ifdefs, which your patch would encourage much more than the source 
> > before.
> 
> Out of curiosity, have you done any more work on that WIP AsciiDoc 
> replacement since you last wrote to the list about it back in October?

Yes.  I rewrote it three times, and the third time is not finished, but 
slowed down to a glacial pace.  You can see the continental shift at my 
repository on repo.or.cz (it's the "dscho" fork of git.git).

Ciao,
Dscho

      reply	other threads:[~2007-11-20 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 18:43 [PATCH] Documentation: fix git-clone manpage not to refer to itself Sergei Organov
2007-11-19 13:35 ` Johannes Schindelin
2007-11-19 14:03   ` Jakub Narebski
2007-11-19 19:18   ` Sergei Organov
2007-11-20  9:41   ` Wincent Colaiuta
2007-11-20 11:28     ` Johannes Schindelin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0711201126430.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=osv@javad.com \
    --cc=win@wincent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).