That's true, but not all projects are structured in a way that is conducive to
this approach, and many people work in repositories for which they do not
control structure.
Additionally, I recently realized this feature is already supported by Xcode 4
(currently in developer preview) as well as
Another solution to conceder would be to check out your project in
parts. Granted this relies heavily on a code structure that would
allow it, but with the right balance of structure, discipline and
svn:externals functionality you can modularize most well formed code
bases.
On Jan 10, 11:45 am,
This is a workaround, but definitely annoying. Command-clicking sometimes
works, but sometimes not. For example, if I want to commit changes to a
directory's properties, but not changes within the directory itself. I end up
having to use Terminal and the --depth option.
I requested the addition
You virtually want a temporary ignore, that resets after the commit. With
perhaps the option I said.
On 10 January 2011 14:22, Jorde Vorstenbosch wrote:
> Cue,
>
> That would indeed be nicer, in addition it should then have a "remember
> last files checked" option or the likes. So that you don't
Cue,
That would indeed be nicer, in addition it should then have a "remember last
files checked" option or the likes. So that you don't have to do that every
time you want to commit. Perhaps something to submit for wanted features?
Jorde
On 10 January 2011 14:11, Cue wrote:
> Jorde, that is cu
Jorde, that is currently my solution but it is an arduous process. I usually
work with working copies that have a large count of files, and quite often find
myself checking-in files whilst excluding others temporarily. But with the
Ignore option it is tremendously simple to overlook those change
Cue,
Permanently/Temporary with ignore. You can always unignore them when you
want to commit them.
Not sure if that is what you mean.
Jorde
On 10 January 2011 13:13, Cue wrote:
> Is there a way to exclude files from a commit? In other words an inverse
> method of what Peter described?
>
> Cue
Cue, actually that's what I want to do as well.
Jorde is correct about the select files ability. However usually I have a dozen
or couple of dozen files spread over multiple folders and I just want to
exclude 1 or 2 files for the moment.
If you could delete files from the commit window some ho
Is there a way to exclude files from a commit? In other words an inverse method
of what Peter described?
Cue
On 10 Jan 2011, at 11:18, Jorde Vorstenbosch
wrote:
> Peter,
>
> Just select the files you want to commit in the browse tab, then hit commit.
>
> Jorde
>
> On 10 January 2011 05:0
Peter,
Just select the files you want to commit in the browse tab, then hit commit.
Jorde
On 10 January 2011 05:02, peterept wrote:
> Often I don't want to commit all the edited/open files that are all in
> the same folder.
>
> Any way to do it? On other clients there is a checkbox on each ite
Often I don't want to commit all the edited/open files that are all in
the same folder.
Any way to do it? On other clients there is a checkbox on each item on
the commit window or you can create multiple working file sets.
Thanks,
Peter
--
You received this message because you are subscribed t
11 matches
Mail list logo
