Re: Resend importinfo patch

[Wu Yongwei]

Hi, I have seen no reply to my message so far. And it's been twenty 
days. *I* can accept Larry's opinions if there are ways to limit the 
import operation to only some specific persons, say, the PM and the main 
developer. If currently it is not possible, any other ways except 
importinfo?

Best regards,

Wu Yongwei

Wu Yongwei wrote:
Larry Jones wrote:
I'd say the tags should go through taginfo (which could be extended if 
people feel that it is necessary to distinguish between the release 
tag and the vendor tag).  The import wouldn't occur until all
of the preliminaries were successful.  I'm still not convinced that
we need a separate importinfo.

-Larry Jones


OK, let's speak about an example. As project manager, I might give the
main developers full access rights to modify any file, but I want that
only *I* have the right to import. I had also a bad experience that a
developer reimported an existing repository: nothing serious happened,
but new (unwanted) branches and tags were created.
That is exactly what I am doing now. My importinfo executes such a
script ("ALL /path/to/import_acls"):
#! /bin/sh
if [ -n $LOGNAME ]; then
  USERNAME=$LOGNAME
elif [ -n $USER ]; then
  USERNAME=$USER
else
  exit 1
fi
if [ $USERNAME != 'adah' ]; then
  echo You are not permitted to import!
  exit 1
fi




_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs