[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[patch #4446] Set execute bits on file via `cvs admin'
From: |
Derek Robert Price |
Subject: |
[patch #4446] Set execute bits on file via `cvs admin' |
Date: |
Mon, 19 Sep 2005 19:06:46 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 |
URL:
<http://savannah.nongnu.org/patch/?func=detailitem&item_id=4446>
Summary: Set execute bits on file via `cvs admin'
Project: Concurrent Versions System
Submitted by: dprice
Submitted on: Mon 09/19/05 at 19:06
Category: None
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Fixed Release: None
Fixed Feature Release: None
_______________________________________________________
Details:
- Desire the ability to deal with execute bits between
'cvs rm' and a new 'cvs add' of the same filename.
Possibly a new admin command to change the execute bits
on the repository file?
https://ccvs.cvshome.org/issues/show_bug.cgi?id=115
>From https://ccvs.cvshome.org/issues/show_bug.cgi?id=115:
I'm using cvs in client-server mode.
When I first "cvs add" a file, if the file is
executable, the server stores it as such,
otherwise is stores it without execute permissions
and subsequent checkout of that file will have
the execute bit set accordingly on the client.
So far so good.
The problem is, that if a file is initially added
while having wrong permissions, those permissions
are stuck forever, and there's no way to correct
them from the client side. Even "cvs delete" and
subsequent "cvs add" of the file with the
executable bit changed has no effect, because the
initial permissions are preserved in the Attic
and are duplicated when the file is re-added.
The enhancement I'm asking for is the following:
When a previously deleted file is "cvs add"ded,
please don't preserve the execute permissions of
the old file in the Attic, but instead apply
whatever the -x/+x permissions of the newly added
file are.
Note that I'm talking about the classic behavior
of cvs regarding the executableness of added
files, nothing to do with the PreservePermissions
feature which doesn't work on client-server
anyway.
Thank you!
------- Additional comments from Alex Manousakis Thu Apr 8 17:04:49 -0700
2004 -------
Any chance this issue can be accepted ? It's been UNCONFIRMED for 1 year
Thank you,
Alex
------- Additional comments from Mark D. Baushke Thu Apr 8 17:13:34 -0700
2004 -------
If you were to checkout the original version of the file
after having done a 'cvs delete' and a 'cvs add' to revive
it, you would see the same permission bits as were on the
original version of the file. This is not a bad thing.
I suppose it might make sense for users to be able to
change the execute bit attributes on the repository file
just as they are able to change the keyword expansion
settings... via the 'cvs admin' command.
A patch to modify the permission bits on the file via
a 'cvs admin' command would be greatfully accepted.
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
mdb@gnu.org | amm2 is original reporter and Mark was
CC'd on original report.
amm2@andrew.cmu.edu | amm2 is original reporter and Mark was
CC'd on original report.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?func=detailitem&item_id=4446>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [patch #4446] Set execute bits on file via `cvs admin',
Derek Robert Price <=