You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Julian Foad (JIRA)" <ji...@apache.org> on 2017/11/22 15:52:00 UTC
[jira] [Updated] (SVN-4705) svn commit --parents option
[ https://issues.apache.org/jira/browse/SVN-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Foad updated SVN-4705:
-----------------------------
Description:
"""
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 specified.
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
{code}
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
{code}
If I then try and commit those files, as sort of a "pre-commit" commit, then i get the error
{code}
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
{code}
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: http://colabti.org/irclogger/irclogger_log/svn?date=2017-11-14#l21
"""
??Sam White (sixquidsquid), 2017-11-14, in [\[RFC\] svn commit --parents option needed|https://lists.apache.org/thread.html/5f65a026d177eee8cf94fbb43d55b7ac7fcaa16bda914eea2d90c31c@%3Cdev.subversion.apache.org%3E]??
was:
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 specified.
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
{code}
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
{code}
If I then try and commit those files, as sort of a "pre-commit" commit, then i get the error
{code}
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
{code}
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: http://colabti.org/irclogger/irclogger_log/svn?date=2017-11-14#l21
??Sam White (sixquidsquid), 2017-11-14, in [\[RFC\] svn commit --parents option needed|https://lists.apache.org/thread.html/5f65a026d177eee8cf94fbb43d55b7ac7fcaa16bda914eea2d90c31c@%3Cdev.subversion.apache.org%3E]??
> svn commit --parents option
> ---------------------------
>
> Key: SVN-4705
> URL: https://issues.apache.org/jira/browse/SVN-4705
> Project: Subversion
> Issue Type: Improvement
> Reporter: Julian Foad
>
> """
> 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 specified.
> 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
> {code}
> 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
> {code}
> If I then try and commit those files, as sort of a "pre-commit" commit, then i get the error
> {code}
> 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
> {code}
> 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: http://colabti.org/irclogger/irclogger_log/svn?date=2017-11-14#l21
> """
> ??Sam White (sixquidsquid), 2017-11-14, in [\[RFC\] svn commit --parents option needed|https://lists.apache.org/thread.html/5f65a026d177eee8cf94fbb43d55b7ac7fcaa16bda914eea2d90c31c@%3Cdev.subversion.apache.org%3E]??
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)