gt;> missing. I would write something like:
>> ...the patterns found in the svn:ignore property apply only to the directory
>> on which that property is set, and not to any of its subdirectories, however
>> it will still be listed by svn propget/proplist commands on subdirec
Den mån 20 mars 2023 kl 21:09 skrev Xsawer xsawer :
> Both are correct in my eyes, just the information, that svn:ingore is
> listed by svn propget/proplist when using parameter --show-inherited-props,
> is missing. I would write something like:
> ...the patterns found in the svn:ign
Both are correct in my eyes, just the information, that svn:ingore is listed
by svn propget/proplist when using parameter --show-inherited-props, is
missing. I would write something like:
...the patterns found in the svn:ignore property apply only to the directory
on which that property is set
rited.
>
+1
>
> -- Původní e-mail --
> Od: Daniel Sahlberg
> Komu: Xsawer xsawer
> Kopie: users@subversion.apache.org
> Datum: 20. 3. 2023 19:44:05
> Předmět: Re: Property svn:ignore reported as inherited by svn proplist
>
> Den mån
: Xsawer xsawer
Kopie: users@subversion.apache.org
Datum: 20. 3. 2023 19:44:05
Předmět: Re: Property svn:ignore reported as inherited by svn proplist
"
Den mån 20 mars 2023 kl 19:04 skrev Xsawer xsawer mailto:xxsa...@seznam.cz)>:
"
Hi,
thank you for quick response.
I would say th
Den mån 20 mars 2023 kl 19:04 skrev Xsawer xsawer :
> Hi,
> thank you for quick response.
> I would say this is kind of gray zone.
> I don't want svn:ignore to be inherited to all the subfolders. Not at all.
> For what svn:global-ignores would be then?
> I only think when
Hi,
thank you for quick response.
I would say this is kind of gray zone.
I don't want svn:ignore to be inherited to all the subfolders. Not at all.
For what svn:global-ignores would be then?
I only think when something is inherited then it is automatically applied.
What else would b
Den mån 20 mars 2023 kl 17:39 skrev Xsawer xsawer :
> Hi,
> Say I have following folder structure:
> main
> - config
>
> Folder main has set property svn:ignore to:
> abc
> def
> ghi
>
> Folder config has no properties set. Property svn:ignore is not
>
Hi,
Say I have following folder structure:
main
- config
Folder main has set property svn:ignore to:
abc
def
ghi
Folder config has no properties set. Property svn:ignore is not inheritable.
I am wondering why is property svn:ignore reported as inherited from folder
main
when
Jon Daley via users wrote on Fri, 26 Aug 2022 13:13 +00:00:
> I don't use Windows, so I can't help you on the escaping of the *, but I
> often use propedit, rather than propset (partly because I can never
> remember the order of the directory and the property value),
Usually (not just in svn) th
On 28.08.2022 14:39, Daniel Sahlberg wrote:
Den fre 26 aug. 2022 kl 15:13 skrev Jon Daley
:
I don't use Windows, so I can't help you on the escaping of the *,
but I
often use propedit, rather than propset (partly because I can never
remember the order of the directory and the pr
Den fre 26 aug. 2022 kl 15:13 skrev Jon Daley :
> I don't use Windows, so I can't help you on the escaping of the *, but I
> often use propedit, rather than propset (partly because I can never
> remember the order of the directory and the property value), so that would
> be easy enough for a one-o
ortoiseSVN, can't you just right-click the
directory and set the property that way and avoid the command-line usage
entirely?
On Fri, 26 Aug 2022, Daniel Sahlberg wrote:
Hi,
Using Subversion "trunk" on Windows built from TortoiseSVN.
I would like to set the svn:ignore property to
Hi,
Using Subversion "trunk" on Windows built from TortoiseSVN.
I would like to set the svn:ignore property to * on a certain directory.
(I'm trying to ignore everything since I'd only want to explicitly add a
few subdirectories).
I thought this would do the trick
C:\wc>
On Wed, Apr 15, 2020 at 2:03 PM Attila Kinali wrote:
>
> On Wed, 15 Apr 2020 13:53:07 +0200
> Branko Čibej wrote:
>
> > I don't remember svn:ignore *ever* working the way you describe. Can you
> > tell us which version of Subversion you were using? Are you absolutel
On Wed, Apr 15, 2020 at 7:28 AM Attila Kinali wrote:
> In the days of old, like several years back...
> When we had files that needed to be edited localy for each user/developer,
> we used to check them in normally, then set svn:ignore to ignore those
> files. This would result `sv
On Wed, 15 Apr 2020 13:53:07 +0200
Branko Čibej wrote:
> I don't remember svn:ignore *ever* working the way you describe. Can you
> tell us which version of Subversion you were using? Are you absolutely
> sure it wasn't modified to behave as you describe?
That was like 10-15
On 15.04.2020 13:27, Attila Kinali wrote:
> Hi,
>
> In the days of old, like several years back...
> When we had files that needed to be edited localy for each user/developer,
> we used to check them in normally, then set svn:ignore to ignore those
> files. This would result `svn
Hi,
In the days of old, like several years back...
When we had files that needed to be edited localy for each user/developer,
we used to check them in normally, then set svn:ignore to ignore those
files. This would result `svn commit` to ignore those files unless
forced to by explicitly
Ryan Schmidt to Anton Shepelev:
>>I have now another question: how do I specify several
>>ignore pattern on the Windows commandline? I have no idea
>>how to pass a list of new-line separated values.
>
>I'd use "svn propedit", and not specify a value on the
>command line; this will open your edito
On Dec 19, 2017, at 06:24, Anton Shepelev wrote:
> I wrote:
>
>> Now, when I modify file.txt, svn still detects the
>> modification and has no problem commiting it. What am I
>> doing wrong?
>>
>> I expect that it will ignore changes to file.txt. If not,
I wrote:
>Now, when I modify file.txt, svn still detects the
>modification and has no problem commiting it. What am I
>doing wrong?
>
>I expect that it will ignore changes to file.txt. If not,
>what is the purpose of svn:ignore?
Got it -- it applies at the moment of
Hello, all
I can't seem to understand the usage of the svn:ignore
property. I have a directory DIR with a file file.txt in
it, which I want ignored. I entered DIR, and typed:
svn propset svn:ignore file.txt .
svn ci .
Now, when I modify file.txt, svn still detects the
modification an
I have another server that I also renamed files on using "svn move"
> but I moved the files one at a time instead of with a script. This
> server reports svn:ignores at revisions after moves were executed
> even though I did not restore a backup.
svn:ignore surely is no
Grok would pick up on.
Thank you,
Scotty
-Original Message-
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Thursday, December 12, 2013 2:11 PM
To: Hinote, Scotty (MSFC-IS40)[NICS]; users@subversion.apache.org
Subject: RE: help with svn:ignore
> I am using Subversion 1.6.11-10 on Re
2013-12-10 20:34:13 + (Tue, 10 Dec 2013) | 1 line set
> svn:ignores
>
> r3 | rancid | 2013-12-10 19:04:29 + (Tue, 10 Dec 2013) | 1 line new
>
> Newer revisions show updates or new router (new file) and there is history
> for all revisi
line
set svn:ignores
r3 | rancid | 2013-12-10 19:04:29 + (Tue, 10 Dec 2013) | 1 line
new
Newer revisions show updates or new router (new file) and there is history for
all revisions past r2041. I executed "svn propdel svn:ignore --revprop -r 2041
file:///opt/rancid/
bt themselves a little less
and answer anyway:
- They probably know that part of Subversion better than the poster
- Posters often get some things wrong (example: "I want to use
global-ignores to avoid merge conflicts", "Why doesn't 'svn ps -F
.gitignore svn:ignore'
g from a trunk to our working copy branch and it
> failed because one of the jar inside /scratch/test/build/jars is causing a
> conflict.
>
> (eg /scratch/testMerge/build/jars/a.jar)
>
> We like to use svn:ignore to ignore the jar files so that the conflict would
> go away in t
Guten Tag Z W,
am Samstag, 27. April 2013 um 18:51 schrieben Sie:
> How do we set it right ?
> Can svn:ignore be used with svn merge or is svn:ignore only used
> for svn checkout as a typical use case for svn:ignore ?
svn:ignore only works on the current versioned directory and
inside /scratch/test/build/jars is causing
a conflict.
(eg /scratch/testMerge/build/jars/a.jar)
We like to use svn:ignore to ignore the jar files so that the conflict
would go away in the next merge.
What's the correct syntax to svn:ignore using it at the root directory.
We have /sc
On Tue, Oct 30, 2012 at 12:55 PM, Vitor Barata wrote:
>
> The problem is that the C files automatically generated for bindings
> are often mixed with standard versioned C files... However, after
> further inspection here, it seems to me that the binding files could
> indeed be put in a separate di
> I'm not quite sure if you really understand the impact of svn:ignore.
> What behaviour are you expecting from the svn:ignore mechanism exactly,
> and how would the expected behaviour impact your workflow?
We want the unversioned files to not show in svn status or in
tortoiseSVN&#
es subversion setting.
We do exactly the same thing in Subversion itself, and we do have
ignore patterns like *.c and so on within the bindings source directories.
There doesn't seem to be any problem with this in our project.
This command lists the patterns we use:
svn propget -v -R svn:ignore
clear that the current ignore system isn't well suited
> for this case, so maybe we should extend Subversion in some way to
> account for this.
The simplest and cleanest way I see to extend Subversion to account
for this is to provide another special property, say svn:localignore,
th
re local file or svn:localignore
> > property or something like that) as well as the versioned svn:ignore
> > property.
>
> But there's none and unless you code this feature on your own you
> won't get it anytime soon, I guess. The only thing left is your build
> sy
Guten Tag Vitor Barata,
am Dienstag, 30. Oktober 2012 um 14:54 schrieben Sie:
> I
> can't help but think that there should be an unversioned list of
> ignored file patterns (.svnignore local file or svn:localignore
> property or something like that) as well as the versioned svn:
en the
current in-development projects and other configuration options. With
CVS, it marked these files as ignored by locally editing the
.cvsignore file inside each folder, which did not have any undesired
effect. Now, with SVN, our first idea was to locally edit each
folder's svn:ignore prope
Guten Tag Vitor Barata,
am Dienstag, 30. Oktober 2012 um 06:58 schrieben Sie:
> Maybe I called our system the wrong name. It is a homemade system, and
> here are some of the things that it does:
Just to be clear: What you call your build system is used directly by
the devs and something we can th
> I don't think I did fully understand the interaction between your
> build system and your devs, as normally build systems like Jenkins,
> Hudson etc. run on a separate server fully automated and per default
> just don't commit anything, therefore it's very unimportant if the
> working copy they a
Guten Tag Vitor Barata,
am Montag, 29. Oktober 2012 um 16:56 schrieben Sie:
> So, I would like to know if anyone has a better idea, and/or
> if anyone agrees that a local .svnignore file (or an extra unversioned
> svn:ignore property) has a good use after all.
I don't thi
> I have searched for this issue in several places, but none of the feature
> requesters presented a scenario like mine, and the overall conclusion was that
> the svn:ignore property was sufficient. However, I stand by the opinion that a
> local .svnignore file is also necessary (
Hello all,
I have searched for this issue in several places, but none of the
feature requesters presented a scenario like mine, and the overall
conclusion was that the svn:ignore property was sufficient. However, I
stand by the opinion that a local .svnignore file is also necessary
(or some
On Mon, Mar 19, 2012 at 10:50 AM, Ryan Schmidt <
subversion-20...@ryandesign.com> wrote:
>
> On Mar 19, 2012, at 12:16, Giulio Troccoli wrote:
>
> > Ok, have you tried ignoring just logs rather than all files, I mean svn
> ps svn:ignore logs ?
>
> The logs direct
On Mar 19, 2012, at 12:16, Giulio Troccoli wrote:
> Ok, have you tried ignoring just logs rather than all files, I mean svn ps
> svn:ignore logs ?
The logs directory has already been added and committed; telling Subversion to
now ignore it will do nothing useful.
t;> Do you mean that the files are shown with an A in the first column?
>
>
> No, they're shown as
>
> ? logs/error.log
> ? logs/access.log
>
> But they're not automagically ignored, even though they match "logs/*"
> which successfully is applied a
g
But they're not automagically ignored, even though they match "logs/*"
which successfully is applied as an svn:ignore pattern on trunk.
Ok, have you tried ignoring just logs rather than all files, I mean svn
ps svn:ignore logs ? As Andy said, the * is expanded by your shell, s
Ahhh Rats. Thanks I missed that.
On Mon, Mar 19, 2012 at 10:13 AM, Mark Phippard wrote:
> in that same directory.
--
This email, including any attachments, is for the sole use of the intended
recipient and may contain confidential information. If you are not the
intended recipient, pleas
On Mon, Mar 19, 2012 at 1:11 PM, Geoff Hoffman wrote:
>
> Mark, I believe you, however I don't see which part of the docs you link
> to addresses this case...
>
This part:
When found on a versioned directory, the svn:ignore property is expected to
contain a list of newli
gh they match "logs/*"
which successfully is applied as an svn:ignore pattern on trunk.
On Mon, Mar 19, 2012 at 9:35 AM, Mark Phippard wrote:
> That is exactly how the feature is supposed to work. Described in book
> here:
>
> http://svnbook.red-bean.com/en/1.7/svn.advan
On Mon, Mar 19, 2012 at 12:26 PM, Geoff Hoffman
wrote:
> I ran into an unexpected behavior with svn:ignore today and wanted to see if
> someone can verify whether this is a bug (in the current version) or just an
> aspect of how Subversion works. We're still on 1.6x.
>
&g
On Mon, Mar 19, 2012 at 12:26, Geoff Hoffman wrote:
> I ran into an unexpected behavior with svn:ignore today and wanted to see if
> someone can verify whether this is a bug (in the current version) or just an
> aspect of how Subversion works. We're still on 1.6x.
>
> Given a
On 19/03/12 16:26, Geoff Hoffman wrote:
I ran into an unexpected behavior with svn:ignore today and wanted to
see if someone can verify whether this is a bug (in the current
version) or just an aspect of how Subversion works. We're still on 1.6x.
Given a tree with
trunk
+
I ran into an unexpected behavior with svn:ignore today and wanted to see
if someone can verify whether this is a bug (in the current version) or
just an aspect of how Subversion works. We're still on 1.6x.
Given a tree with
trunk
+ cache
+ htdocs
+ logs
+ system
I have
On Thu, 15 Mar 2012 02:06:08 +, Daniel Shahaf wrote:
> Andreas Krey wrote on Wed, Mar 14, 2012 at 15:33:35 +0100:
...
> > But the real strange thing: I did only do a merge; not actually
> > edit any properties myself.
> >
>
> So? Propchanges are merged too.
Yes, but they weren't modified (b
x27;:
> Cannot accept non-LF line endings in 'svn:ignore' property
>
> For one it would really helpful to know which of the seventeen
> svn:ignore properties is the culprit.
>
It's probably an easy patch to libsvn_repos/fs-wrap.c.
> But the real strange thing:
On Wed, 14 Mar 2012 15:33:35 +, Andreas Krey wrote:
...
> Cannot accept non-LF line endings in 'svn:ignore' property
...
> Even worse: There are only 0a (LF) line endings in the ignore properties.
> No 0d (CR) in sight; at least in the output of 'svn pg svn:ignore&#
Hi,
the full glory:
svn: E175008: Commit failed (details follow):
svn: E175008: At least one property change failed; repository is unchanged
svn: E175002: Error setting property 'ignore':
Cannot accept non-LF line endings in 'svn:ignore' property
For one it would re
Please keep idscussion on the mailing list by using Reply All. My reply below:
On Sep 9, 2011, at 08:17, Randy Paries wrote:
> On Thu, Sep 8, 2011 at 10:46 PM, Ryan Schmidt wrote:
>>
>>
>> svn:ignore is for ignoring unversioned files that you do not want to commit
>>
; so when i do a svn up i want to ignore or not update
> userdirs and below
> inc/settings.php
>
> i have created a file in / called svnIgnoreFiles.me
> i then did
>
> [root@moosejaw html]# svn propset svn:ignore -F svnIgnoreFiles.me .
> property 'svn:ignore' set o
a file in / called svnIgnoreFiles.me
i then did
[root@moosejaw html]# svn propset svn:ignore -F svnIgnoreFiles.me .
property 'svn:ignore' set on '.'
i delete userdirs/*
but when i do a svn up it still brings down from svn all the userdirs
what part am i missing??
thanks
Randy
On 12/02/2010 10:23 AM, Steve Cohen wrote:
On 12/01/2010 12:29 PM, Steve Cohen wrote:
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as *.o which
On 12/01/2010 12:29 PM, Steve Cohen wrote:
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as *.o which may
be found in any number of directories
On Dec 2, 2010, at 08:43, Luke Imhoff wrote:
> On Thu, 2010-12-02 at 00:31 -0600, Daniel Shahaf wrote:
>> svn:ignore patterns are apr_fnmatch() patterns, and apr_fnmatch() does
>> accept regex-like [a-z] expressions in its patterns, so you could try
>>
>> [a-z][a-
e. Is there a pattern specifier that would embrace all files
> > > without an extension?
> >
> > I can't think of a way to do that.
> >
>
> svn:ignore patterns are apr_fnmatch() patterns, and apr_fnmatch() does
> accept regex-like [a-z] expressions in
Steve Cohen wrote on Thu, Dec 02, 2010 at 07:48:05 -0600:
> On 12/02/2010 12:23 AM, Daniel Shahaf wrote:
>> You can use 'propedit --editor-cmd=script.sh **/', where script.sh
>> appends '*.o' to argv[1].
>>
> Does svn propset svn:ignore accept the *
7;sed -i s/foo/bar/' svn:log
Steve Cohen wrote on Wed, Dec 01, 2010 at 12:29:58 -0600:
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as
; >
> > abcde
> > fghqp
> >
> > etc.
> >
> > I believe that * will match any files with or without periods so it isn't
> > suitable. Is there a pattern specifier that would embrace all files
> > without an extension?
>
> I can't thi
Steve Cohen wrote on Wed, Dec 01, 2010 at 17:40:12 -0600:
> On 12/01/2010 03:33 PM, Ryan Schmidt wrote:
>> On Dec 1, 2010, at 15:19, Steve Cohen wrote:
>>
>>> It seems to me that
>>> svn --recursive propset svn:ignore xyz
>>>
>>> is basica
e on Wed, Dec 01, 2010 at 12:29:58 -0600:
> I have a need to define a number of svn:ignore patterns in my project.
>
> Some are specific directories somewhere in my project tree. Others are
> particular file types created by a build process such as *.o which may
> be found in a
On 12/01/2010 03:33 PM, Ryan Schmidt wrote:
On Dec 1, 2010, at 15:19, Steve Cohen wrote:
It seems to me that
svn --recursive propset svn:ignore xyz
is basically just syntactic sugar for manually going through issuing
svn propset svn:ignore xyz
on every node of the directory
On Dec 1, 2010, at 15:19, Steve Cohen wrote:
> It seems to me that
> svn --recursive propset svn:ignore xyz
>
> is basically just syntactic sugar for manually going through issuing
> svn propset svn:ignore xyz
>
> on every node of the directory structure, It
tory) that you could svn:ignore everything in?
Sadly, no, not without a major rewrite of the build process. This is deep
legacy stuff, using make, with the typical pattern of mixing source and object
in the same directory. Not the way I would have designed it but ...
Then you may have
Redirecting this discussion back to the mailing list..
On Dec 1, 2010, at 14:05, Steve Cohen wrote:
> On 12/01/2010 01:38 PM, Ryan Schmidt wrote:
>> Can you have the build process write its files to a different directory (a
>> "build" directory) that you could
ou have the build process write its files to a different directory (a
"build" directory) that you could svn:ignore everything in?
th or without periods so it isn't
> suitable. Is there a pattern specifier that would embrace all files without
> an extension?
I can't think of a way to do that.
> Alternatively, one common differentiating aspect of these files is that they
> have executable privileges.
brace all
files without an extension?
Alternatively, one common differentiating aspect of these files is that
they have executable privileges. Being able to svn:ignore based on this
would be a nice feature to have.
On Dec 1, 2010, at 12:29, Steve Cohen wrote:
> I have a need to define a number of svn:ignore patterns in my project.
>
> Some are specific directories somewhere in my project tree. Others are
> particular file types created by a build process such as *.o which may be
> foun
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as *.o which may
be found in any number of directories.
However, the svn propset command only
rg
> Subject: uses of svn:ignore ?
>
> Hi all,
>
> I want to ignore a config file located in my working copy at
> ./application/config/config.php . So, in command-line I type
> the following :
>
> $ cd application/config
> $ svn propset svn:ignore config.php .
> pro
Hi all,
I want to ignore a config file located in my working copy at
./application/config/config.php . So, in command-line I type the following :
$ cd application/config
$ svn propset svn:ignore config.php .
property 'svn:ignore' set on '.'
### and I can check
$ sv
On 09/02/2010 12:51, Janosch Scharlipp wrote:
Is the runtime part of the final program, or is it available as a dll in my
os ready to be loaded on program startup?
In build lingo, that sounds: is the runtime statically linked or
dynamically linked? It depends on how the subversion source code
On Mon, Feb 8, 2010 at 3:40 AM, Janosch Scharlipp <
janosch.scharl...@isys-vision.de> wrote:
>
> Hi, i am trying to set the svn:ignore property of a specific folder to "*",
> so that all files and folders inside this folder are beeing ignored by svn.
> Somehow i don&#
re be
documentend, how i can escape characters like the star, to prevent
expansion?
Janosch
-Ursprüngliche Nachricht-
Von: Stefan Sperling [mailto:s...@elego.de]
Gesendet: Dienstag, 9. Februar 2010 11:40
An: Janosch Scharlipp
Cc: users@subversion.apache.org
Betreff: Re: Problems setting svn:i
On Tue, Feb 09, 2010 at 11:27:21AM +0100, Janosch Scharlipp wrote:
>
> Thanks for your answers, but still i think this is not as it should be.
> If the parameter is expanded by the shell, or as if it was the shell, then
> the shell escaping mechanism (^ on windows) should work.
> If parameter expa
On Feb 9, 2010, at 11:27 AM, Janosch Scharlipp wrote:
>
> Thanks for your answers, but still i think this is not as it should be.
> If the parameter is expanded by the shell, or as if it was the shell, then
> the shell escaping mechanism (^ on windows) should work.
> If parameter expansion takes
this parameter should not be expanded.
Janosch
-Ursprüngliche Nachricht-
Von: Stefan Sperling [mailto:s...@elego.de]
Gesendet: Sonntag, 7. Februar 2010 22:25
An: Janosch Scharlipp
Cc: users@subversion.apache.org
Betreff: Re: Problems setting svn:ignore property to "*" via windo
On Sun, Feb 07, 2010 at 08:40:19PM +0100, Janosch Scharlipp wrote:
>
> Hi, i am trying to set the svn:ignore property of a specific folder to "*",
> so that all files and folders inside this folder are beeing ignored by svn.
> Somehow i don't get this done, i tried
Hi, i am trying to set the svn:ignore property of a specific folder to "*",
so that all files and folders inside this folder are beeing ignored by svn.
Somehow i don't get this done, i tried lots of different aproaches, but it
always seems as if the pattern is beeing expanded, so
> On Wed, Feb 3, 2010 at 5:28 PM, GF wrote:
> Hello everyone.
> I've two question about svn:ignore
>
> 1) I've a file that MUST exist in the repository in its "default"
> version, but i don't want that people to commit any local change to
>
On Wed, Feb 3, 2010 at 5:28 PM, GF wrote:
> Hello everyone.
> I've two question about svn:ignore
>
> 1) I've a file that MUST exist in the repository in its "default"
> version, but i don't want that people to commit any local change to
> it. Is there a
t; To: users@subversion.apache.org
> Subject: svn:ignore an existing file
>
> Hello everyone.
> I've two question about svn:ignore
>
> 1) I've a file that MUST exist in the repository in its "default"
> version, but i don't want that people to commit any local
1) I've a file that MUST exist in the repository in its "default"
version
Then forget svn:ignore - it doesn't apply to versioned files.
You could lock the file in each branch where it occurs, or set the
svn:lock property, to make it more difficult for others to tamper
Hello everyone.
I've two question about svn:ignore
1) I've a file that MUST exist in the repository in its "default"
version, but i don't want that people to commit any local change to
it. Is there a way to have this behaviour with svn:ignore?
I mean that with "
94 matches
Mail list logo
