You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Straw, Scott J" <Sc...@UNISYS.com> on 2006/07/20 14:41:02 UTC
svn_load_dirs.pl: Why is it setting svn:executable on everything?
I imported a code drop into our repository with svn_load_dirs.pl, but I
was surprised that it decided to set the svn:executable property on
EVERY file (header files, C files, Makefiles, anything). I didn't
intentionally set up any set of special instructions for setting
properties (i.e., a configuration file specified with a -p option).
Was this a good thing, or a problem?
Thanks,
- Scott
Re: svn_load_dirs.pl: Why is it setting svn:executable on everything?
Posted by Gary Thomas <ga...@mlbassoc.com>.
Straw, Scott J wrote:
> I imported a code drop into our repository with svn_load_dirs.pl, but I
> was surprised that it decided to set the svn:executable property on
> EVERY file (header files, C files, Makefiles, anything). I didn’t
> intentionally set up any set of special instructions for setting
> properties (i.e., a configuration file specified with a –p option).
Look at the files you imported - svn_load_dirs.pl only sets
the svn:executable property based on what it finds there.
n.b. if you got these files from a Windows file system (FAT),
then the execute permission bit often gets set gratuitously.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: svn_load_dirs.pl: Why is it setting svn:executable on everything?
Posted by "Straw, Scott J" <Sc...@UNISYS.com>.
Huh ...
It turns out that the tarball I received the code drop in had the
executable bit set for every single file. The script was just doing
what it was supposed to do, I guess. I'll have to talk to our OEM about
their code drops...
Thanks!
- Scott
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006c@ryandesign.com]
Sent: Thursday, July 20, 2006 10:16 AM
To: Straw, Scott J
Cc: users@subversion.tigris.org
Subject: Re: svn_load_dirs.pl: Why is it setting svn:executable on
everything?
On Jul 20, 2006, at 16:41, Straw, Scott J wrote:
> I imported a code drop into our repository with svn_load_dirs.pl,
> but I was surprised that it decided to set the svn:executable
> property on EVERY file (header files, C files, Makefiles,
> anything). I didn't intentionally set up any set of special
> instructions for setting properties (i.e., a configuration file
> specified with a -p option).
>
>
>
> Was this a good thing, or a problem?
Yeah, I noticed that too, now that you mention it. I don't see why
it's doing that especially.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn_load_dirs.pl: Why is it setting svn:executable on everything?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jul 20, 2006, at 16:41, Straw, Scott J wrote:
> I imported a code drop into our repository with svn_load_dirs.pl,
> but I was surprised that it decided to set the svn:executable
> property on EVERY file (header files, C files, Makefiles,
> anything). I didn’t intentionally set up any set of special
> instructions for setting properties (i.e., a configuration file
> specified with a –p option).
>
>
>
> Was this a good thing, or a problem?
Yeah, I noticed that too, now that you mention it. I don't see why
it's doing that especially.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org