I don't have kernel without the ea patch. But I tried
it on tmpfs and the result is the same 0754.
> > Oh, it is linux 2.4.31 on ext3(with user attribute
> > patches), if that makes a difference.
>
> I don't know if this might make difference, but is
> it also possible to
> test this on plain ex
On Tue, 13 Sep 2005, gary ng wrote:
BTW, what would be the reason to ignore the
metadata(the file attribute in this case) as they are
just part of the *nix system, unlike Windows that is
not very important.
IIRC, there were some discussion about this on some of darcs mailing list
in the past,
I am running 1.0.3 from debian sid.
Well, even it only looks into the content of the file
to determine
if it is script, it still cannot explain why it does
0755 to 0754.
Without the flag, it just gives 0644.
BTW, what would be the reason to ignore the
metadata(the file attribute in this case) as
On Tue, 13 Sep 2005, Tommy Pettersson wrote:
Also, the --set-script-executable feature seems to have be
broken in some 1.0.4 prerelease, so it only works in 1.0.3.
True! And I promised to work on it, which I do, but just few minutes per
day as my spare time allows. Anyway, I still hope to be
On Tue, 13 Sep 2005, gary ng wrote:
umask 0022, so every file I create is by default
0744(just touch a). I changed it to 0755.
Just found another thing, darcs don't consider changes
to file attributes as change. I need to change the
attribute, then change the content of the file and
follows by
On Tue, Sep 13, 2005 at 05:26:48AM -0700, gary ng wrote:
> Just found another thing, darcs don't consider changes
> to file attributes as change. I need to change the
> attribute, then change the content of the file and
> follows by a darcs record to record the changes.
>
> But the darcs get still
umask 0022, so every file I create is by default
0744(just touch a). I changed it to 0755.
Just found another thing, darcs don't consider changes
to file attributes as change. I need to change the
attribute, then change the content of the file and
follows by a darcs record to record the changes.
On Mon, 12 Sep 2005, gary ng wrote:
Hi,
I have a file with 0755 in the source directory, but
when I do a darcs get --set-scripts-executable dir1
dir2, the file in dir2 has mode 0754.
Is this intended ?
What's your umask? Haven't you played with it after creating file with 755
perms in dir1?
Hi,
I have a file with 0755 in the source directory, but
when I do a darcs get --set-scripts-executable dir1
dir2, the file in dir2 has mode 0754.
Is this intended ?
thanks and regards,
gary
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
h
> ...
> a) `darcs --set-scripts-executable` is an option that must be supplied
> to Darcs when you *do* a get. You can cause this to be the default
> behaviour of Darcs for you if you add
>
> get --set-scripts-executable
>
> to ~/.darcs/defaults [why this isn't just the default behaviour of
On Sat, Aug 20, 2005 at 11:30:50PM +1000, Andrew Cowie wrote:
> b) There was a bug in darcs 1.0.2 regarding this: while this option
> worked correctly for local gets, it didn't work when doing a remote get.
> This appears to be fixed in 1.0.3
It's broken again in 1.0.4... and it's not so very easy
On Fri, 2005-19-08 at 22:00 -0700, Frederik Eaton wrote:
> Putting the line
> get set-scripts-executable
> in _darcs/prefs/defaults in my repository doesn't seem to have the
> effect ...
Couple things:
a) `darcs --set-scripts-executable` is an option that must be supplied
to Darcs when you *do* a
Putting the line
ALL set-scripts-executable
or
get set-scripts-executable
in _darcs/prefs/defaults in my repository doesn't seem to have the
effect of causing files which are executable in the repository to show
up as executable after a 'darcs get'.
Also, what is the purpose of erasing the exe
On Wed, Jun 08, 2005 at 12:47:55PM +0900, Stephen J. Turnbull wrote:
> > "Tommy" == Tommy Pettersson <[EMAIL PROTECTED]> writes:
> Tommy> So, to get what you want you'll have to ask everyone to put
> Tommy> this flag in their default file.
>
> For one flag it's equivalent IIRC, but if
> "Tommy" == Tommy Pettersson <[EMAIL PROTECTED]> writes:
Tommy> The --set-scripts-executable flag is a hack (or clever
Tommy> simplifications) to handle the executable property of files
Tommy> in the repo. Yes, it _is_ a bit odd it gets handled as a
Tommy> personal setting an
On Tue, Jun 07, 2005 at 11:30:19AM +0200, Remko Troncon wrote:
> Hi,
>
> I put the following line in my _darcs/prefs/defaults file:
> get set-scripts-executable
> expecting that people who get my repository would have all their scripts
> executable, but alas, this is not what happens :-( Is
Hi,
I put the following line in my _darcs/prefs/defaults file:
get set-scripts-executable
expecting that people who get my repository would have all their scripts
executable, but alas, this is not what happens :-( Is this expected ?
cheers,
Remko
_
17 matches
Mail list logo
