From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Barkalow Subject: Re: [ANNOUNCE] GIT 1.5.3-rc4 Date: Sat, 4 Aug 2007 00:57:03 -0400 (EDT) Message-ID: References: <7vzm18jg7p.fsf@assigned-by-dhcp.cox.net> <200708040341.36147.ismail@pardus.org.tr> <7vsl70jdcr.fsf@assigned-by-dhcp.cox.net> <46B3F762.1050306@midwinter.com> <7vfy2zj4nj.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Steven Grimm , Ismail =?utf-8?Q?D=C3=B6nmez?= , git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Sat Aug 04 06:57:26 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1IHBhd-0001De-B1 for gcvg-git@gmane.org; Sat, 04 Aug 2007 06:57:25 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752027AbXHDE5I (ORCPT ); Sat, 4 Aug 2007 00:57:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752013AbXHDE5I (ORCPT ); Sat, 4 Aug 2007 00:57:08 -0400 Received: from iabervon.org ([66.92.72.58]:3761 "EHLO iabervon.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752025AbXHDE5H (ORCPT ); Sat, 4 Aug 2007 00:57:07 -0400 Received: (qmail 26022 invoked by uid 1000); 4 Aug 2007 04:57:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Aug 2007 04:57:03 -0000 In-Reply-To: <7vfy2zj4nj.fsf@assigned-by-dhcp.cox.net> Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Fri, 3 Aug 2007, Junio C Hamano wrote: > If I read you correctly, what you are proposing to offer is a > clone of asciidoc, perhaps AsciiDoc 7, with only xhtml11 and man > backends. It is a subset in the sense that you will do only two > backends, but otherwise is a clone in the sense that you are > going to implement the input language we use (one thing I > personally care about while probably other people do not is the > conditional compilation "ifdef::stalenotes[]" in git.txt). It's worth noting that we're a substantial portion of the asciidoc user base, at least based on asciidoc's "Projects using AsciiDoc" page. We could probably be influential in the asciidoc development if we tried (maybe starting with a config file mechanism for controlling what characters are markup instead of literal, so that we'll be able to make documents which will work the same with all versions of asciidoc). -Daniel *This .sig left intentionally blank*