FYI - cvs-import.sh changes

[Josh Boyer]

On Wed, 2007-04-11 at 11:40 +0200, Matthias Saou wrote:
> Christian Iseli wrote :
> 
> > It was noticed that the cvs-import script gets used by many folks, not
> > only for actually importing a new package into CVS, but also for
> > importing new versions of an existing package.
> > 
> > This latter usage led to a few cases where changes made in CVS got
> > silently lost when the updated package was imported.
> > 
> > After some discussions (like disallowing the use of cvs-import
> > for anything else than initial import) it was decided to modify the
> > script to at least show a diff of what's currently in CVS with what's
> > going to be imported (so that there is a chance the maintainer will
> > notice changes about to be undone), and will ask the maintainer to
> > enter a commit message.
> > 
> > Thanks to Jens Petersen for implementing the changes.
> 
> This is definitely a good thing.
> 
> FWIW, I'm not even using that script anymore : Now that the CVS
> branches need to be "manually" created by the CVS admins, I simply do a

"manually"?  Why the quotes?  I can assure you it's definitely a manual
process. :)

josh