"C. Michael Pilato" <cmpil...@collab.net> writes: > On 04/17/2013 06:43 AM, Philip Martin wrote: >> [dev CC'd] >> >> Nick <nos...@codesniffer.com> writes: >> >>> The 'patch' subcommand does not seem to support applying a changelist >>> description to the files that are part of the patch. Any plans to >>> support this? >>> >>> (Should I be asking this on the dev list?) >> >> That sounds like a useful feauture. The list of files affected by patch >> is not always readily available to pass to the changelist command. >> >> Would this behaviour be useful for other commands? > > Most of our other commands have explicitly provided targets, so adding a > changelist to those targets is a simple modification to the previous command > issued at the prompt. > > For some commands, the targets aren't all explicit, but the resulting set is > trivial to reproduce with 'svn changelist' anyway. For example, you could > run 'svn propset -R svn:eol-style=native', which will only touch files, but > then 'svn changelist -R' will likewise touch those same files. > > 'svn merge' comes to mind as one that, like patch, does not always have > explicitly named targets.
Yes, merge is another candidate for this behaviour. > It might be convenient for users if we supplied a sort of > "add-affected-items-to-this-changelist" option to all of our > schedule-a-working-copy-change types of subcommands. The behaviour looks simple to define for 'patch' and 'merge', I was thinking about 'svn add --force' which marks all the unversioned files for addition. I don't know which files a user would expect to be added to the changelist? Just the newly added files, all the added files, all the files? -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
