Tab completing URL arguments in the shell (was: Re: Automatically supply the origin URL in svn merge)

2020-03-26 Thread Daniel Shahaf
Stefan Sperling wrote on Thu, 26 Mar 2020 21:02 +00:00: > The ultimate goal here is to allow users to type less characters when > starting merges. Scripting tab-completion for SVN URL arguments into > your favourite shell would also be a usable and effective solution. What would the algorithm be?

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Daniel Shahaf
Stefan Sperling wrote on Thu, 26 Mar 2020 10:45 +0100: > On Thu, Mar 26, 2020 at 01:10:25AM +0300, Anton Shepelev wrote: > > Daniel Shahaf: > > > However, I can also see circumstances in which this smartness > > > could be counter-productive: > > > > > > 1. In repository restructurings, such as

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Stefan Sperling
On Thu, Mar 26, 2020 at 08:46:35PM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Thu, 26 Mar 2020 10:45 +0100: > > Renames are modelled as copy+delete in SVN. > > They are, but we can behave differently depending on whether or not the > adding-with-history was accompanied by a deletion

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Daniel Shahaf
Stefan Sperling wrote on Thu, 26 Mar 2020 22:02 +0100: > On Thu, Mar 26, 2020 at 08:46:35PM +, Daniel Shahaf wrote: > > Stefan Sperling wrote on Thu, 26 Mar 2020 10:45 +0100: > > > Renames are modelled as copy+delete in SVN. > > > > They are, but we can behave differently depending on

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Daniel Shahaf
Stefan Sperling wrote on Thu, 26 Mar 2020 11:15 +0100: > On Thu, Mar 26, 2020 at 01:10:25AM +0300, Anton Shepelev wrote: > > Daniel Shahaf: > > > however, I don't think the lack of these distinctions is > > > necessarily a blocker. It just means we need to be more careful > > > about not

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Anton Shepelev
Stefan Sperling: > It's not that simple, as the conflict resolver demonstates. > You're not taking cases into account where multiple copies within > a signle revision correspond to a single deletion. > > So if you want to handle that then you must either error out when > the heuristic fails, or

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Anton Shepelev
Daniel Shahaf: > Yes, this feature won't happen unless someone invests time in > making it happen -- but let's not discourage people from > discussing feature ideas even if they may not personally have > time to implement them. Discussions are just as useful a > contribution as patches. It is

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Stefan Sperling
On Thu, Mar 26, 2020 at 01:10:25AM +0300, Anton Shepelev wrote: > Daniel Shahaf: > > However, I can also see circumstances in which this smartness > > could be counter-productive: > > > > 1. In repository restructurings, such as running «svn merge» in a > > working copy of ^/thebarproject/trunk

Re: Automatically supply the origin URL in svn merge

2020-03-26 Thread Stefan Sperling
On Thu, Mar 26, 2020 at 01:10:25AM +0300, Anton Shepelev wrote: > Daniel Shahaf: > > however, I don't think the lack of these distinctions is > > necessarily a blocker. It just means we need to be more careful > > about not writing automation that will help some cases and > > backfire in others.