Date: Wed, 19 Jun 1996 19:00:12 +0000 (GMT) From: Adam David <adam@veda.is> To: joerg_wunsch@uriah.heep.sax.de Cc: adam@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-CVSROOT@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT modules Message-ID: <199606191900.TAA13566@veda.is> In-Reply-To: <199606182111.XAA09472@uriah.heep.sax.de> from J Wunsch at "Jun 18, 96 11:11:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > Modified: . modules > > Log: > > attempt #5 > > might I suggest for easy-import to allow the import to continue even if the > > modules entry has already been created? > > The existing module name is taken as an indication that you're going > to import on a vendor branch. (How else should branches be handled?) After studying the source carefully, I now see that the extra commits to the modules file could have been avoided simply by specifying a vendor-branch import with "non-vendor-branch" tags. The only improvement that I can suggest now is either to document this feature at the top of the file, something like: When importing after an incomplete previous attempt which already created the modules entry, specify a vendor-branch import with "normal import" tags. or to change the prompt question to something more general such as: (for vendor-branch import, etc.) use the existing module path? It's rather ugly perhaps, but easier to make sense of. -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606191900.TAA13566>