Sam White wrote:
> I propose the addition of an equivalent to the --parents option to "svn
> commit", to check in the directory structure as well as any files
Thank you for posting here. You already know from IRC that I support
this proposal. I filed an 'enhancement' issue in the tracker:
https://issues.apache.org/jira/browse/SVN-4705 . Unfortunately we can't
make any promises about when or if anyone will implement it. Volunteers
are needed :-/
> I understand that with svn add, the --parents option is available.
> However, the use case I have in mind is one that I come across quite
> often, involving changelists and SVN moves.
> If I add files to changelist, I expect to be able to commit any changes
> to them quickly and easily - that's the point, right? But if I perform
> an SVN move on these items, to a directory which is not yet committed,
> because I cannot yet add directories to the changelist, when I go to
> commit the files, I get the error
> svn: E200009: '/some/new/directory/here' is not known to exist in the
> repository and is not part of the commit, yet its child
> '/some/new/directory/here/file_on_changelist.txt' is part of the commit
> If I then try and commit those files, as sort of a "pre-commit" commit,
> then i get the error
> Cannot commit '/some/directory/here' because it was moved from
> '/other/directory/here/' which is not part of the commit; both sides of
> the move must be committed together
> The workaround for this seems to involve a mess of committing these
> directories together, with the option --depth=empty, and then committing
> with the changelist. Alternatively, I could just skip the --depth=empty,
> and let the commit handle the fiels as well - but then, what was the
> point in making a changelist? I still end up formulating some long command!
> I was asking about this in the #svn IRC - here is the chat log:
> Is what I am suggesting clear? I'd appreciate your thoughts.
> Sam (sixquidsquid)
Received on 2017-11-17 13:49:08 CET