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 absolutely
> > sure it wasn't modified t
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 `svn commit` to i
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 years ago. I don't r
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 commit` to ignore
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,
>> what is the purpose of svn:ignore?
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 'svn add'. I have now
anoth
Johan Corveleyn wrote on Sat, Apr 27, 2013 at 20:18:07 +0200:
> [ Small meta-suggestion: please drop the "quick question" suffix from
> your future posts. It's distracting, and often the answers aren't that
> quick to come up with :-). And because of this, you scare away some
> potential helpers, w
On Sat, Apr 27, 2013 at 6:51 PM, Z W wrote:
> Hi All
>
> We like to ignore a set of jar files under our working copy root directory:
> working copy root dir: /scratch/testMerge
> working copy jars dir: /scratch/testMerge/build/jars
>
> We tried to perform merging from a trunk to our workin
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 only for
object
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.
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 **/filename idiom as a legitimate
> pattern indic
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].
Another example, the following is a "Fix typo in the log message" idiom:
% svn propedit --revprop -r69426 --editor-cmd 'sed -i s/foo/bar/' svn:log
Steve Cohe
You can use 'propedit --editor-cmd=script.sh **/', where script.sh
appends '*.o' to argv[1].
Another example, the following is a "Fix typo in the log message" idiom:
% svn propedit --revprop -r69426 --editor-cmd 'sed -i s/foo/bar/' svn:log
Steve Cohen wrote on Wed, Dec 01, 2010 at 12:29:58 -0600:
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
> found in any number of
> 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 way to have this behaviour with svn:ignor
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 way to have this behaviour with svn:ignore?
>
Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851VAT Reg No 778499447
-Original Message-
> From: GF [mailto:gan...@gmail.com]
> Sent: 03 February 2010 09:29
> To: users@subversion.apache
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 with
it. But in my exper
20 matches
Mail list logo
