On Wed, Mar 14, 2012 at 9:00 PM, Les Mikesell wrote:
> On Wed, Mar 14, 2012 at 7:29 PM, Nico Kadel-Garcia
> wrote:
> > On Wed, Mar 14, 2012 at 9:33 AM, Qazwart wrote:
> >>
> >> What if you deliver your source code *outside* of your revision control
> >> system? This is quite common for open sou
On Wed, Mar 14, 2012 at 7:29 PM, Nico Kadel-Garcia wrote:
> On Wed, Mar 14, 2012 at 9:33 AM, Qazwart wrote:
>>
>> What if you deliver your source code *outside* of your revision control
>> system? This is quite common for open source projects. If I can't trust the
>> build process to do a clean,
On Wed, Mar 14, 2012 at 9:33 AM, Qazwart wrote:
> What if you deliver your source code *outside* of your revision control
> system? This is quite common for open source projects. If I can't trust the
> build process to do a clean, I'm in trouble.
>
> What if you don't use a build process? Just to
On Wed, 14 Mar 2012 11:52:33 +, Simon Dean wrote:
...
> I use Rake and Gradle (migrated to Gradle from Maven). Rake is used for .NET
> codebases and Gradle for Java. It's very easy for files to slip through a
> "clean" task.
Actually the whole notion of a 'clean task' is misleading. Any
ubversion.apache.org
> Subject: RE: Feature request - SVN command to clean a working copy of all
> unversioned and ignored files and directories
>
> > -Original Message-
> > From: David Weintraub [mailto:qazw...@gmail.com]
> > Sent: woensdag 14 maart 2012 2:14
>
nd to clean a working copy of all
> unversioned and ignored files and directories
>
> On Mon, Mar 12, 2012 at 1:05 PM, Simon Dean
> wrote:
> > I suspect TortoiseSVN uses the official Subversion client code under the
> hood. There's no way they'd
> > re-imple
On Tue, 13 Mar 2012 21:14:04 +, David Weintraub wrote:
...
> So, it's possible for someone to write a Subversion client that does
> do a "clean up".
So, what you're saying is that, because it is possible to implement
'svn cleanup' on top of the svn client libs, the official svn client
won't ge
On Mon, Mar 12, 2012 at 1:05 PM, Simon Dean
wrote:
> I suspect TortoiseSVN uses the official Subversion client code under the
> hood. There's no way they'd
> re-implement a whole SVN client from scratch.
I don't know if Tortoise uses any Subversion command line client code,
but TortoiseSVN doe
On Mon, Mar 12, 2012 at 12:32 PM, David Weintraub wrote:
> Here's why I don't think this is a feature for the Subversion project:
>
> * This is a Subversion client function and not a function of
> Subversion itself. Subversion thoughtfully publishes a Subversion API
>
So far, yes. That doesn't me
On Mon, Mar 12, 2012 at 05:11:40PM +, Simon Dean wrote:
> Not having contributed to SVN before, I don't really know how the SVN
> client(s) are implemented. How much of the code in the various Windows and
> Linux SVN command line clients (e.g. CollabNet's Windows command line client,
> Slik
> -Original Message-
> From: Simon Dean
> Sent: 12 March 2012 17:05
> To: 'David Weintraub'; Nico Kadel-Garcia
> Cc: Les Mikesell; Andreas Krey; Giulio Troccoli; users@subversion.apache.org
> Subject: RE: Feature request - SVN command to clean a working copy of all
&
kesell; Andreas Krey; Giulio Troccoli; Simon Dean;
> users@subversion.apache.org
> Subject: Re: Feature request - SVN command to clean a working copy of all
> unversioned and ignored files and directories
>
> Here's why I don't think this is a feature for the Subversion proj
Here's why I don't think this is a feature for the Subversion project:
* This is a Subversion client function and not a function of
Subversion itself. Subversion thoughtfully publishes a Subversion API
that developers can use to create their own Subversion clients. Notice
that TortoiseSVN does not
On Sun, Mar 11, 2012 at 9:19 PM, Les Mikesell wrote:
> On Sun, Mar 11, 2012 at 5:28 PM, Nico Kadel-Garcia
> wrote:
> >
> >> Subversion probably isn't the best VCS to use if you can't arrange
> >> reasonable connectivity to the repository to make clean checkouts
> >> feasible.
> >
> >
> > Been th
On Sun, Mar 11, 2012 at 5:28 PM, Nico Kadel-Garcia wrote:
>
>> Subversion probably isn't the best VCS to use if you can't arrange
>> reasonable connectivity to the repository to make clean checkouts
>> feasible.
>
>
> Been there, done that, got my wrist slapped for questioning the mandated
> stand
On Sun, Mar 11, 2012 at 2:41 PM, Les Mikesell wrote:
> On Sun, Mar 11, 2012 at 1:10 PM, Andreas Krey wrote:
> > ...
> >> That seems wrong or at least unnecessarily inconvenient for a CI
> >> setup.
> >
> > You're a bit hung up on the 'CI' token. That isn't the only situation
> > where a 'svn cle
Konstantin Kolinko wrote on Sun, Mar 11, 2012 at 01:56:45 +0400:
> If you use svn 1.7 (that is you have only ".svn" directory) it is easy to
> 1. just delete everything
> 2. do your "svn revert".
>
> The revert will restore missing files and folders from their pristine copies.
>
>
> It would not
On Sun, Mar 11, 2012 at 1:10 PM, Andreas Krey wrote:
> ...
>> That seems wrong or at least unnecessarily inconvenient for a CI
>> setup.
>
> You're a bit hung up on the 'CI' token. That isn't the only situation
> where a 'svn cleanup' can be useful.
Subversion probably isn't the best VCS to use i
On Sun, 11 Mar 2012 11:23:34 +, Les Mikesell wrote:
...
> That seems wrong or at least unnecessarily inconvenient for a CI
> setup.
You're a bit hung up on the 'CI' token. That isn't the only situation
where a 'svn cleanup' can be useful.
> And if you are doing it by hand, why not just delete
On Sun, Mar 11, 2012 at 12:15 AM, Nico Kadel-Garcia wrote:
>>
>> > Except for the part where not everyone should be forced to reinvent
>> > the wheel of 'put the sandbox in a pristine state' as in 'cd ..;
>> > rm -r $sandboxname; svn checkout -r $rev $url $sandboxname', but more
>> > efficiently a
On Sat, Mar 10, 2012 at 4:50 PM, Les Mikesell wrote:
> On Sat, Mar 10, 2012 at 2:13 PM, Andreas Krey wrote:
> >>
> > Except for the part where not everyone should be forced to reinvent
> > the wheel of 'put the sandbox in a pristine state' as in 'cd ..;
> > rm -r $sandboxname; svn checkout -r $r
2012/3/9 Simon Dean :
> Hi
>
> Are there any plans to add a command to SVN that cleans a working copy or
> path of all unversioned and/or ignored files and directories?
>
> This is a very common need for automated Continuous Integration builds where
> a working copy is reu
On Sat, Mar 10, 2012 at 2:13 PM, Andreas Krey wrote:
>>
> Except for the part where not everyone should be forced to reinvent
> the wheel of 'put the sandbox in a pristine state' as in 'cd ..;
> rm -r $sandboxname; svn checkout -r $rev $url $sandboxname', but more
> efficiently and without hitting
On 3/10/2012 12:13 PM, Andreas Krey wrote:
On Sat, 10 Mar 2012 10:47:55 +, Les Mikesell wrote:
...
I'd argue that tools have no business removing any files they didn't
create unless you name them explicitly. And that complicated things
that you want a CI to automate should be scripted with
On Sat, 10 Mar 2012 10:47:55 +, Les Mikesell wrote:
...
> I'd argue that tools have no business removing any files they didn't
> create unless you name them explicitly. And that complicated things
> that you want a CI to automate should be scripted with the script
> managed in your VCS anyway
On Fri, Mar 9, 2012 at 5:25 PM, Andreas Krey wrote:
>
> If you argue that a CI/XY tool should find out for itself what files are
> not under svn control then one could argue analogously that it should
> as well bypass svn for doing updates. :-)
I'd argue that tools have no business removing any f
On Fri, 09 Mar 2012 11:53:47 +, Les Mikesell wrote:
...
> > So the CI would rely on another piece of software, SVN in this case, to
> > know what it has created in terms of files. Well, it doesn't seem right
> > to me.
>
> So how would you propose doing this across different VCS? I don't see
On Fri, Mar 9, 2012 at 2:56 PM, Simon Dean
wrote:
> Hi
>
> Are there any plans to add a command to SVN that cleans a working copy or
> path of all unversioned and/or ignored files and directories?
>
> This is a very common need for automated Continuous Integration builds where
Another unconventional way of accomplishing this would be to use Bazaar's
clean-tree command. With the bzr-svn plugin installed, you should be able to
directly operate on SVN working trees:
bzr clean-tree --ignored --unknown --detritus --force
> On Fri, Mar 09, 2012 at 10:45:13AM -0700, Geoff Hoffman wrote:
> > A couple of things I find interesting... the bug tracker you linked to
> > is 3 years old and still on tigris.org. Assuming that is still the
> > valid place for tracking subversion features & bugs?
>
> The issue tracker has not
On Fri, Mar 9, 2012 at 11:34 AM, Stefan Sperling wrote:
> On Fri, Mar 09, 2012 at 10:45:13AM -0700, Geoff Hoffman wrote:
> > A couple of things I find interesting... the bug tracker you linked to
> is 3
> > years old and still on tigris.org. Assuming that is still the valid
> place
> > for tracki
On Fri, Mar 09, 2012 at 10:45:13AM -0700, Geoff Hoffman wrote:
> A couple of things I find interesting... the bug tracker you linked to is 3
> years old and still on tigris.org. Assuming that is still the valid place
> for tracking subversion features & bugs?
The issue tracker has not been migrate
2012/3/9 Giulio Troccoli :
>
>>> But maybe I'm missing something?
>> A CI implementation would have to implement it specifically each VCS as it
>> would have to call the VCS to found out what files/directories are
>> unversioned and ignored.
>
> So the CI would rely on another piece of software,
On Fri, Mar 9, 2012 at 10:24 AM, Stefan Sperling wrote:
> On Fri, Mar 09, 2012 at 01:56:34PM +, Simon Dean wrote:
> > Hi
> >
> > Are there any plans to add a command to SVN that cleans a working copy
> or path of all unversioned and/or ignored files and directories
On Fri, Mar 09, 2012 at 01:56:34PM +, Simon Dean wrote:
> Hi
>
> Are there any plans to add a command to SVN that cleans a working copy or
> path of all unversioned and/or ignored files and directories?
There is a related open feature request in our issue t
On Fri, 09 Mar 2012 14:10:39 +, Giulio Troccoli wrote:
...
> Sorry, but to me this has got nothing to do with Subversion.
'course it does. It knows which files are to be ignored, and thus
can be savely thrown away, and it does know which files are not
under version control, and thus should be
> -Original Message-
> From: Giulio Troccoli [mailto:giulio.trocc...@mediatelgroup.co.uk]
> So the CI would rely on another piece of software, SVN in this case, to know
> what it has created in terms of files. Well, it doesn't seem right to me.
With TortoiseSVN providing this functionality
On 09/03/12 15:03, Simon Dean wrote:
>> From: Giulio Troccoli [mailto:giulio.trocc...@mediatelgroup.co.uk]
>>
>> Why would the CI implement a different solution for each VCS? Those, I
>> understand, are files created during the build process, they have got nothing
>> to do with SVN or any other V
the feature (quoted from
http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-cleanup.html)
Delete unversioned files and folders, Delete ignored files and folders
==
This is a fast and easy way to r
On 09/03/12 14:35, Simon Dean wrote:
From: Giulio Troccoli [mailto:giulio.trocc...@mediatelgroup.co.uk]
Sorry, but to me this has got nothing to do with Subversion. Your CI tool is
should clean up itself.
Having said that, if someone wants to implement such feature I don't think I
would have
> From: Bob Archer [mailto:bob.arc...@amsi.com]
>
> FYI: If you are on windows the TortoiseSVN client's "Clean up" function
> allows you to delete unversioned and ignored files if you want. Also, it
> allows
> you to revert all changes when you clean up as well.
> From: Giulio Troccoli [mailto:giulio.trocc...@mediatelgroup.co.uk]
>
> Sorry, but to me this has got nothing to do with Subversion. Your CI
> tool is should clean up itself.
>
> Having said that, if someone wants to implement such feature I don't
> think I would have anything against it. But I
> Hi
>
> Are there any plans to add a command to SVN that cleans a working copy or
> path of all unversioned and/or ignored files and directories?
>
> This is a very common need for automated Continuous Integration builds where
> a working copy is reused for multiple r
On 09/03/12 13:56, Simon Dean wrote:
Hi
Are there any plans to add a command to SVN that cleans a working copy or path
of all unversioned and/or ignored files and directories?
This is a very common need for automated Continuous Integration builds where a
working copy is reused for multiple
Hi
Are there any plans to add a command to SVN that cleans a working copy or path
of all unversioned and/or ignored files and directories?
This is a very common need for automated Continuous Integration builds where a
working copy is reused for multiple runs of the same build. Currently
> The updated version of that page of documentation for the current
> version of Subversion is:
>
> http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html
>
> Good to know, thanks. Unfortunately Google returned the 1.1
> version of the doc for my query. For different queries, I see the
On Mon, 2010-12-20 at 07:48 -0600, Ryan Schmidt wrote:
> The updated version of that page of documentation for the current
> version of Subversion is:
>
> http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html
Good to know, thanks. Unfortunately Google returned the 1.1 version of
the d
On Dec 20, 2010, at 01:05, Nick wrote:
> You can also ignore files so they don't show up in svn operations (like
> svn status). This is accomplished via the svn:ignore property. See SVN
> properties (http://svnbook.red-bean.com/en/1.1/ch07s02.html) for more
> info.
Let's not refer people to the
On Sat, Dec 18, 2010 at 09:39:55AM -0800, sajan wrote:
> hi
> is there any way I can avoid adding particular folders/files when I
> add my code to subversion.In git you can do that using .gitignore
> file.
>
> suppose I have this directory structure
>
> mycode
> |tobeignored1
> |tobei
On Sat, 2010-12-18 at 09:39 -0800, sajan wrote:
> hi
> is there any way I can avoid adding particular folders/files when I
> add my code to subversion.In git you can do that using .gitignore
> file.
>
> suppose I have this directory structure
>
> mycode
> |tobeignored1
> |tobeincluded
hi
is there any way I can avoid adding particular folders/files when I
add my code to subversion.In git you can do that using .gitignore
file.
suppose I have this directory structure
mycode
|tobeignored1
|tobeincluded
|---tobeignored2
|---myimage.jpg
|---tobeincluded2
|---myli
51 matches
Mail list logo
