Re: Reapply patch lost during recent "blind import" oflibtool

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

On Thu, 12 Apr 2001, Loren James Rittle wrote:
> In addition to any English description, a good place to document this
> policy might be in CVSROOT/commitinfo and a supporting script script.
> We could write a simple rule in commitinfo to help enforce this policy
> and the existing policy which covers config.guess (this example could
> be extended to handle other special cases mentioned in your policy
> documentation patch):
>
> /cvs/gcc/.* true
> /cvs/gcc check-import
>
> Here is a sample check-import:
>
> #!/bin/sh
>
> W1="WARNING: This file should be upgraded from the related external"
> W2="WARNING: master source repository using 'cvs import'."
> W3="WARNING: See http://gcc.gnu.org/codingconventions.html for details."
>
> shift; for i in $*; do case $i in
>   config.guess) echo $W1; echo $W2; echo $W3; exit 1;;
>   config.sub) echo $W1; echo $W2; echo $W3; exit 1;;
>   ltconfig) echo $W1; echo $W2; echo $W3; exit 1;;
>   ltmain.sh) echo $W1; echo $W2; echo $W3; exit 1;;
>   libtool.m4) echo $W1; echo $W2; echo $W3; exit 1;;
>   ltcf-*.sh) echo $W1; echo $W2; echo $W3; exit 1;;
> esac; done


On 12 Apr 2001, Alexandre Oliva wrote:
> I don't have a strong opinion about this.  At first, I like the idea
> of enforcing import-only updates.  On the other, it would seem to
> prevent temporary work-arounds for problems, whenever the maintainers
> of libtool become unresponsive.  Well, one can always import files
> that consist solely of a single patch, instead of a full import, so we
> don't really lose any abilities, whereas we gain warnings for those
> who don't know about the rules.
>
> Yeah, the more I think about this, the more I like it.

So, how about setting up Loren's script?

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/