Re: svnmucc --revision 0 no longer works when creating a file

2020-07-23 Thread Daniel Shahaf
sebb wrote on Thu, 23 Jul 2020 11:18 +0100: > On Thu, 23 Jul 2020 at 01:17, Daniel Shahaf wrote: > > You can either parse stderr despite this complication, or use the > > API directly, in which case you'll sidestep this complication entirely > > (you'll get just one integer, rather than two). >

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-23 Thread sebb
On Thu, 23 Jul 2020 at 01:17, Daniel Shahaf wrote: > > sebb wrote on Wed, 22 Jul 2020 22:34 +0100: > > On Wed, 22 Jul 2020 at 17:46, Nathan Hartman > > wrote: > > > > > > On Wed, Jul 22, 2020 at 12:10 PM sebb wrote: > > > > > Use the machine-parseable E42 error codes. That's exactly what >

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-22 Thread Daniel Shahaf
sebb wrote on Wed, 22 Jul 2020 22:34 +0100: > On Wed, 22 Jul 2020 at 17:46, Nathan Hartman wrote: > > > > On Wed, Jul 22, 2020 at 12:10 PM sebb wrote: > > > > Use the machine-parseable E42 error codes. That's exactly what > > > > they're for. (which-error.py and svn_error_symbolic_name()

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-22 Thread sebb
On Wed, 22 Jul 2020 at 17:46, Nathan Hartman wrote: > > On Wed, Jul 22, 2020 at 12:10 PM sebb wrote: > > > Use the machine-parseable E42 error codes. That's exactly what > > > they're for. (which-error.py and svn_error_symbolic_name() can be used > > > to convert numbers to symbolic names.)

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-22 Thread Nathan Hartman
On Wed, Jul 22, 2020 at 12:10 PM sebb wrote: > > Use the machine-parseable E42 error codes. That's exactly what > > they're for. (which-error.py and svn_error_symbolic_name() can be used > > to convert numbers to symbolic names.) > > Where are these error codes defined? > I could not find an

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-22 Thread sebb
On Sun, 12 Jul 2020 at 18:13, Daniel Shahaf wrote: > > sebb wrote on Sun, 12 Jul 2020 16:55 +0100: > > On Sun, 12 Jul 2020 at 15:26, Daniel Shahaf wrote: > > > > > > sebb wrote on Tue, 07 Jul 2020 20:43 +0100: > > > > When I first started using svnmucc, it used to be the case that > > > > svnmucc

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-12 Thread Daniel Shahaf
sebb wrote on Sun, 12 Jul 2020 16:55 +0100: > On Sun, 12 Jul 2020 at 15:26, Daniel Shahaf wrote: > > > > sebb wrote on Tue, 07 Jul 2020 20:43 +0100: > > > When I first started using svnmucc, it used to be the case that > > > svnmucc 'put' --revision 0 would fail if the target file already > > >

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-12 Thread sebb
On Sun, 12 Jul 2020 at 15:26, Daniel Shahaf wrote: > > sebb wrote on Tue, 07 Jul 2020 20:43 +0100: > > When I first started using svnmucc, it used to be the case that > > svnmucc 'put' --revision 0 would fail if the target file already > > existed. This no longer happens. > > > > Is the file-to-be

Re: svnmucc --revision 0 no longer works when creating a file

2020-07-12 Thread Daniel Shahaf
sebb wrote on Tue, 07 Jul 2020 20:43 +0100: > When I first started using svnmucc, it used to be the case that > svnmucc 'put' --revision 0 would fail if the target file already > existed. This no longer happens. > Is the file-to-be's parent directory the root directory? If that isn't the case, t

svnmucc --revision 0 no longer works when creating a file

2020-07-07 Thread sebb
When I first started using svnmucc, it used to be the case that svnmucc 'put' --revision 0 would fail if the target file already existed. This no longer happens. The previous behaviour was very useful, so are there any plans to reinstate it? I don't think there is a straightforward way to guarant