Re: Fishing for a General Permissions API (inspired by "importers"

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark D. Baushke wrote:

> Extending the commitinfo would be acceptable to me provided that access
> to both the vendor and version tags to be used for the import were also
> somehow made available to make the decision to allow the import to happen
> or not.


Good point again, Mark.  It should be useful and easy enough to extend
the current commitinfo hook to include a format string for the
destination branch name anyhow, and this could be reused for import's
vendor branch.  Even including the old revision for each file would be
easy.  Destination revision would be harder - it currently isn't set for
use by loginfo until it is retrieved after the actual commit.

As for the _list_ of release tags (don't forget it is a list), this
could be done, but would be a little more compilcated.  Perhaps if it
were simply left empty for calls to commit and filled in for calls to
import, that would be sufficient.  Using some characters forbidden in
tags, users could specify something like the following so that their
scripts could handle the double lists:

ALL $CVSROOT/CVSROOT/myscript %r %p $T %{t} -- %{sV}

I've annotated Issuezilla with our last few comments again.

Derek
- --
                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAVyvlLD1OTBfyMaQRAmTJAJ91eqQExFyawOElH+KF+mU4YumbxQCfch1z
HZ/oD4nw0ekks9GFUqZH6Ws=
=fmQ4
-----END PGP SIGNATURE-----