On Fri, Jun 26, 2009 at 04:30:01PM -0600, Ali Bahrami wrote:
>  Richard Lowe wrote:
> > Will Fiveash <William.Fiveash at Sun.COM> writes:
> >> While we are on the subject, is it feasible/reasonable for the hg cdm
> >> extension checks to support some form of exemption lists that are found
> >> in the repository?  The idea is that instead of having personalized
> >> *.NOT files, there would be a set of standard check exemption list files
> >> located in a standard path as part of the gate repository source which
> >> the hg cdm check commands would consult.  These lists would be part of
> >> the hg repository and would get pull'ed when one creates a local repo.
> > This is almost exactly what Ali did when implementing mapfilechk I
> > believe.
> > 6800164 Standard file exclusion mechanism needed for Cadmium tools
> > -- Rich
> > _______________________________________________
> > scm-migration-dev mailing list
> > scm-migration-dev at opensolaris.org
> > http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev
> 
> 
>     I believe that all you need to do is create a file in the exception_lists
>  subdirectory of the workspace, using the same format as the mapfilechk
>  exception file that's already there, and Cadmium will apply those
>  rules to the files it passes to the command.
> 
>  This is the same format used by the hg .NOT files.
> 
>  Of course, I only have one data point (mapfilechk) to support that
>  claim, so let us know...  :-)

Sure, I'm interested in creating various *.NOT files for the Solaris krb
code that we port over from MITKC.  I'll look into this and let y'all
know the outcome.

-- 
Will Fiveash
Sun Microsystems               Office x64079/512-401-1079
Austin, TX, 78727              (TZ=CST6CDT), USA
Internal Solaris Kerberos/GSS/SASL website: http://kerberos.sfbay.sun.com
http://opensolaris.org/os/project/kerberos/

Reply via email to