* David Kastrup (2006-12-25) writes: > Ralf Angeli <[EMAIL PROTECTED]> writes: > >> I guess for importing something like >> cvs -z3 -d:ext:<membername>@cvs.savannah.nongnu.org:/sources/auctex \ >> import -m "Import of RefTeX 4.31" reftex FSF REFTEX_4_31 >> should work. I'm not sure about vendor and release tag. For the >> release tag perhaps the format we are using for AUCTeX would be >> better: release_4_31. > > I am not sure that importing is the right thing to do. If I > understand the CVS docs correctly, this produces a branch, but we'd > rather want to have this added into HEAD.
The Cederquist 1.11.13 I have here has this to say at the start of chapter 13 on page 79: "Use the import command to create and update the vendor branch. When you import a new file, the vendor branch is made the `head' revision, so anyone that checks out a copy of the file gets that revision. When a local modification is committed it is placed on the main trunk, and made the `head' revision." > Does anybody have a clue who we could ask about this? savannah-hackers? > With regard to > releases: using the same kind of tags as for the rest of AUCTeX seems > like a plan, but we should keep RefTeX out of the AUCTeX > _distribution_ (tarballs, top Makefile etc) at first, I would think, > even though we'll have it be a top-level subdirectory. Subdirectory? I would have created it as a module, that means on the same level as `auctex' in the CVS repo. -- Ralf _______________________________________________ auctex-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/auctex-devel
