git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Francesco Pretto <ceztkoml@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Documentation: enhanced "git for CVS users" doc about shared repositories
Date: Wed, 7 Nov 2007 11:47:48 -0500	[thread overview]
Message-ID: <20071107164748.GA10525@fieldses.org> (raw)
In-Reply-To: <277490E5-2B9A-4BA7-9DD7-C1CEE698B348@zib.de>

On Wed, Nov 07, 2007 at 09:07:58AM +0100, Steffen Prohaska wrote:
> On Nov 7, 2007, at 1:46 AM, Francesco Pretto wrote:
>
>> Junio C Hamano ha scritto:
>>>
>>> Honestly speaking, I am not too thrilled about making the
>>> cvs-migration document much longer than what it currently is.
>>>
>
> Maybe the description of setting up a shared repository should
> go to the user-manual and cvs-migration should refer to the
> user-manual, instead of the other way round. I don't like the
> idea that the user-manual is referring to a CVS specific guide.
> The user manual should be as self-contained as possible.

I'd be interested in patches that did that.  If somebody wants to work
on that, they might want to start with

	git://linux-nfs.org/~bfields/git.git docwork-foreign-scms

which has the skeleton of an "interoperating with foreign scms" chapter.

The thing that's kept me from working on this in the past is that it's a
bit of a step backwards for someone that *just* wants to get to the
cvs-migration stuff, since now it may appear you have to plow through
the rest of the manual to get to it.

We could address that with clearer dependency information ("before
reading this chapter, read chapters 1 and 3..."), and/or by providing
some more links (e.g. repopulate the howto directory with links to some
chapters that address popular questions).

--b.

      reply	other threads:[~2007-11-07 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 22:32 [Patch] Documentation: enhanced "git for CVS users" doc about shared repositories Francesco Pretto
2007-11-05 23:52 ` Junio C Hamano
2007-11-06 10:04   ` Francesco Pretto
2007-11-06 10:53     ` Johannes Schindelin
2007-11-06 11:14       ` Francesco Pretto
2007-11-06 21:44   ` [PATCH] " Francesco Pretto
2007-11-06 23:25     ` Junio C Hamano
2007-11-07  0:46       ` Francesco Pretto
2007-11-07  0:55         ` Johannes Schindelin
2007-11-07  1:10           ` Francesco Pretto
2007-11-07  1:36           ` Aghiles
2007-11-07  7:35             ` Steffen Prohaska
2007-11-07  8:45               ` Andreas Ericsson
2007-11-07  9:09           ` David Kastrup
2007-11-07 17:32           ` J. Bruce Fields
2007-11-07  8:03         ` Wincent Colaiuta
2007-11-07  8:07         ` Steffen Prohaska
2007-11-07 16:47           ` 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=20071107164748.GA10525@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ceztkoml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=prohaska@zib.de \
    /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).