git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Matt Graham <mdg149@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Linked glossary from cvs-migration page
Date: Wed, 23 Apr 2008 12:50:11 -0400	[thread overview]
Message-ID: <20080423165011.GE31576@fieldses.org> (raw)
In-Reply-To: <1208956431-1955-1-git-send-email-mdg149@gmail.com>

On Wed, Apr 23, 2008 at 09:13:51AM -0400, Matt Graham wrote:
> Coming from CVS, I found the git glossary vital to learning git and learning
> how terms in git correlate to the cvs terminology with which I am familiar.
> 
> This patch links the glossary from the cvs-migration page so cvs users will
> be able to fine the glossary as soon as they start looking at git documents.
> 
> Signed-off-by: Matt Graham <mdg149@gmail.com>

Fine by me.--b.

> ---
>  Documentation/cvs-migration.txt |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
> index ea98900..00f2e36 100644
> --- a/Documentation/cvs-migration.txt
> +++ b/Documentation/cvs-migration.txt
> @@ -8,7 +8,8 @@ designating a single shared repository which people can synchronize with;
>  this document explains how to do that.
>  
>  Some basic familiarity with git is required.  This
> -link:tutorial.html[tutorial introduction to git] should be sufficient.
> +link:tutorial.html[tutorial introduction to git] and the
> +link:glossary.html[git glossary] should be sufficient.
>  
>  Developing against a shared repository
>  --------------------------------------
> -- 
> 1.5.5.49.gf43e2
> 

      reply	other threads:[~2008-04-23 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 13:13 [PATCH] Linked glossary from cvs-migration page Matt Graham
2008-04-23 16:50 ` J. Bruce Fields [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=20080423165011.GE31576@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mdg149@gmail.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).