From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] CVS 1.11.23
Date: Thu, 12 Sep 2013 18:22:21 +0200 [thread overview]
Message-ID: <067dfd66423ab9e0765def2e092a6d72@proxima.alt.za> (raw)
Should anyone find it useful, I have repaired CVS where it insisted in
creating files (on import and add/commit, seemingly) with empty
permissions.
The expression in src/import.c:1444,1448
mode = (sb.st_mode |
(sb.st_mode & S_IRWXU) >> 3 |
(sb.st_mode & S_IRWXU) >> 6) &
~cvsumask &
~(S_IWRITE | S_IWGRP | S_IWOTH);
must lose the ~ in front of cvsumask. How it got there and why no one
has fixed it is a bit of a mystery to me.
I haven't yet made sure that my copy of the sources is faithful to the
release - it's been a long time since I last looked into this - but if
anyone wants me to dump the sources as they stand in their direction,
just drop me a line, preferably here on 9fans or on my google mail
account: lucio.dere is the account.
++L
reply other threads:[~2013-09-12 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=067dfd66423ab9e0765def2e092a6d72@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).