From: Jakub Narebski <jnareb@gmail.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: Git in a Nutshell guide
Date: Wed, 21 Nov 2007 22:32:33 +0100 [thread overview]
Message-ID: <200711212232.33791.jnareb@gmail.com> (raw)
In-Reply-To: <20071121194507.GA3569@efreet.light.src>
Dnia środa 21. listopada 2007 20:45, Jan Hudec napisał:
> On Wed, Nov 21, 2007 at 00:57:28 +0100, Jakub Narebski wrote:
>> 2. Git has some historical cruft, including the fact that it began as
>> series of low level tools (plumbing) and became proper SCM (acquired
>> proper porcelain) later, what can be even now seen in documentation...
What I meant here that some of important documentation can be only
found in plumbing commands man pages.
>> 3. Explanation of some features (like object model) would be much easier
>> with some graphics (diagrams etc.), but chosen documentation format,
>> AsciiDoc, doesn't make it easy...
>
> I dare to disagree here. Asciidoc supports generating image tags for
> respective output formats and it really does not look hard. We could have
> PNGs and if we wanted higher press quality even SVG or EPS and convert them
> to PNGs for the HTML version (and use EPS for latex output).
The problem is that 1) language used to generate images must be easy
to understand and readable in text form (so sources are enough to
understand); 2) one of the main formats is manpage (although that would
not matter for "Git Guide" / "The Git Book").
Should we choose PIC? Or perhaps DOT? I can write little MetaPost, but
I don't think that would be good format for git diagrams, even if it
can be converted to PDF, SVG and PNG.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-11-21 21:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 13:05 Git in a Nutshell guide Jonas Juselius
2007-11-19 13:29 ` Jakub Narebski
2007-11-19 14:33 ` Jonas Juselius
2007-11-22 8:22 ` David Kågedal
2007-11-23 9:28 ` Jakub Narebski
2007-11-19 15:02 ` Brian Downing
2007-11-19 15:03 ` Brian Downing
2007-11-19 15:48 ` Nicolas Pitre
2007-11-19 16:05 ` Jakub Narebski
2007-11-19 16:14 ` Jonas Juselius
2007-11-19 16:49 ` Benoit Sigoure
2007-11-19 22:01 ` Daniel Barkalow
2007-11-20 11:34 ` Jonas Juselius
2007-11-20 23:57 ` Jakub Narebski
2007-11-21 19:45 ` Jan Hudec
2007-11-21 21:32 ` Jakub Narebski [this message]
2007-11-22 16:37 ` jhud7196
2007-11-22 13:15 ` Jonas Juselius
2007-11-22 14:19 ` Jonathan del Strother
2007-11-22 14:24 ` Johannes Schindelin
2007-11-22 16:57 ` jhud7196
2007-11-19 16:45 ` Lars Hjemli
2007-11-19 16:56 ` Jonas Juselius
2007-11-19 16:57 ` Benoit Sigoure
2007-11-19 17:04 ` Lars Hjemli
2007-11-19 18:10 ` Benoit Sigoure
2007-11-19 18:13 ` J. Bruce Fields
2007-11-19 18:13 ` Matthieu Moy
2007-11-19 18:35 ` [PATCH] Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys Matthieu Moy
2007-11-19 20:13 ` Junio C Hamano
2007-11-19 20:28 ` Matthieu Moy
2007-11-19 20:31 ` Matthieu Moy
2007-11-19 21:15 ` Git in a Nutshell guide Benoit Sigoure
2007-11-19 21:33 ` Matthieu Moy
2007-11-19 21:51 ` Benoit Sigoure
2007-11-19 22:23 ` J. Bruce Fields
2007-11-19 22:29 ` Junio C Hamano
2007-11-19 22:59 ` Matthieu Moy
2007-11-19 23:07 ` Junio C Hamano
2007-11-19 17:05 ` Matthieu Moy
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=200711212232.33791.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
/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).