From: Petr Baudis <pasky@suse.cz>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH Cogito] Fix README asciidoc formatting
Date: Tue, 11 Oct 2005 23:43:18 +0200 [thread overview]
Message-ID: <20051011214318.GY22079@pasky.or.cz> (raw)
In-Reply-To: <20051002105601.GB9934@diku.dk>
Dear diary, on Sun, Oct 02, 2005 at 12:56:01PM CEST, I got a letter
where Jonas Fonseca <fonseca@diku.dk> told me that...
> BTW, what about adding some notatation info for those boxes? It looks
> very creative for an introduction document.
What do you mean by "notation info"?
> commit ca52918a9a6e02e55d878d8f5e68672432940337
> tree 60d270e8b45beeee9361b13284ff2eefec746fd6
> parent 9356837de630644323c800e2accad2618d7393f9
> author Jonas Fonseca <fonseca@diku.dk> Sun, 02 Oct 2005 12:45:03 +0200
> committer Jonas Fonseca <fonseca@antimatter.(none)> Sun, 02 Oct 2005 12:45:03 +0200
>
> README | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/README b/README
> --- a/README
> +++ b/README
> @@ -305,11 +305,13 @@ will `cg-clone` do?
>
> +--------+
> +--------+
> +
> First it creates an empty repository
>
> +--------+
> $ origin<
> +--------+
> +
> Then it creates an 'origin' head, and will copy all the history from the
> remote repository's 'master' head there. So this head exists to reflect
> the state of the remote repository. The important point is that it is
..snip..
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-10-11 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 10:56 [PATCH Cogito] Fix README asciidoc formatting Jonas Fonseca
2005-10-11 21:43 ` Petr Baudis [this message]
2005-10-12 14:22 ` Jonas Fonseca
2005-10-21 1:18 ` Petr Baudis
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=20051011214318.GY22079@pasky.or.cz \
--to=pasky@suse.cz \
--cc=fonseca@diku.dk \
--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).