Re: tests/test-base64.c: executable?

[Mark D. Baushke]

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

Jim Meyering <address@hidden> writes:

> address@hidden (Larry Jones) wrote:
> > Jim Meyering writes:
> >> Simon Josefsson <address@hidden> wrote:
> >> > Here too.  Is this possible to fix without direct access to the CVS
> >> > repository?
> >>
> >> Yep, but it's a kludge.
> >> Remove it and re-add without the execute bit set.
> >
> > I don't think that works -- CVS only sets the execute permissions on
> > the repository file when it first creates it.
> 
> You're right.
> I just tried it in a temporary repository.
> Thanks for keeping me honest :-)
> 
> So I don't know how to do it, and suspect it's not possible.

If/when we ever manage to release cvs 1.12.14, you will be able to use
'cvs admin --no-execute test-base64.c' to make the change. 

I believe that the patch to do this work in an existing set of CVS
sources is on CVS patch #4446 on savannah.nongnu.org.

(I do not know when Derek will finish with the outstanding bits left to
finish and generate a cvs 1.12.14 release. Of course, after the release
it may take some time before savannah installes a 1.12.14 release.)

> Recently, for coreutils, I had a similar problem.
> I committed a new test script _without_ execute permissions.
> Luckily, I have access to the master copy of that repository,
> so was able to change it there and let it propagate to savannah.
> 
> Yet another reason to switch to git.

There are many reasons and tradeoffs related to using cvs versus git.
However, I would probably not add this particular reason to the list.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFbPFACg7APGsDnFERAqauAJ9duxC5RdxEOIiG2vh5iVtvuh5IewCgsXxX
w0eNi5/HUsXWd2/xiwI/ehc=
=YEy8
-----END PGP SIGNATURE-----