Re: [PATCH] Documentation: reorganize cvs-migration.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, 6 Dec 2006, J. Bruce Fields wrote:

> Modify cvs-migration.txt so it explains first how to develop against a 
> shared repository, then how to set up a shared repository, then how to 
> import a repository from cvs.  Though this seems chronologically 
> backwards, it's still readable in this order, and it puts the more 
> commonly needed material closer to the front.

This is a laudable goal, and the order makes sense (put first that what 
most people are interested in).

A few comments:

- just skimming the patch, I found "commiting" (needs another "t"), and 
  "-bare" (needs another "-").

- It might make more sense to "git init-db --shared" and fetch the initial 
  revision into it, rather than clone it and then fix. You might also want
  to mention that the "--shared" of -clone is different in meaning from 
  that of -init-db (make just a footnote of it, to avoid intimidating 
  readers).

- By far the easiest method to import from cvs is to go to a checked out
  _CVS_ working directory, and just say "git cvsimport".

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]