On Fri, 24 Jul 2020 at 07:06, Daniel Shahaf wrote:
>
> Daniel Sahlberg wrote on Fri, 24 Jul 2020 05:53 +00:00:
> > Den fre 24 juli 2020 01:46sebb skrev:
> > > I am suggesting that 'add' functionality could be added to svnmucc itself.
> > > This would make it more versatile, especially for use in
Daniel Sahlberg wrote on Fri, 24 Jul 2020 05:53 +00:00:
> Den fre 24 juli 2020 01:46sebb skrev:
> > I am suggesting that 'add' functionality could be added to svnmucc itself.
> > This would make it more versatile, especially for use in shell scripts.
>
> Unless I'm mistaken, add is a purely
Den fre 24 juli 2020 01:46sebb skrev:
> I am suggesting that 'add' functionality could be added to svnmucc itself.
> This would make it more versatile, especially for use in shell scripts.
>
Unless I'm mistaken, add is a purely local action within a working copy.
And the point with svnmucc is
On Thu, 23 Jul 2020 at 23:44, Daniel Shahaf wrote:
>
> sebb wrote on Thu, 23 Jul 2020 11:30 +0100:
> > On Thu, 23 Jul 2020 at 00:59, Daniel Shahaf wrote:
> > >
> > > sebb wrote on Wed, 22 Jul 2020 22:44 +0100:
> > > > The SVN put command can add a new file or update an existing one.
> > > >
> >
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).
>
sebb wrote on Thu, 23 Jul 2020 11:30 +0100:
> On Thu, 23 Jul 2020 at 00:59, Daniel Shahaf wrote:
> >
> > sebb wrote on Wed, 22 Jul 2020 22:44 +0100:
> > > The SVN put command can add a new file or update an existing one.
> > >
> > > As part of a batch update it may be necessary to ensure that a
On Thu, 23 Jul 2020 at 00:59, Daniel Shahaf wrote:
>
> sebb wrote on Wed, 22 Jul 2020 22:44 +0100:
> > The SVN put command can add a new file or update an existing one.
> >
> > As part of a batch update it may be necessary to ensure that a
> > particular file will be created and not updated - or
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
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()
sebb wrote on Wed, 22 Jul 2020 22:44 +0100:
> The SVN put command can add a new file or update an existing one.
>
> As part of a batch update it may be necessary to ensure that a
> particular file will be created and not updated - or vice versa.
> That is currently not at all easy to do, which is
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
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
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
> > > >
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
> > >
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
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,
Nevermind.
Seeing that /usr/local/lib was included in the compile line as "rpath", I tried
moving all existing libsvn_* files from /usr/local/lib to an "old_1.11"
directory (they came from the 1.11 compilation)
After that, "make" just went fine.
Regards,
Juanga
Sam Ruby wrote on Mon, 05 Jun 2017 14:24 -0400:
> On 06/05/2017 02:10 PM, Daniel Shahaf wrote:
> > Sam Ruby wrote on Mon, 05 Jun 2017 10:08 -0400:
> >> When I moved whimsy from Ubuntu 14.04 (svn 1.8.8) to Ubuntu 16.04 (svn
> >> 1.9.3), svnmucc commands started failing for me:
> >>
> >> $ svnmucc
On 06/05/2017 02:10 PM, Daniel Shahaf wrote:
Sam Ruby wrote on Mon, 05 Jun 2017 10:08 -0400:
When I moved whimsy from Ubuntu 14.04 (svn 1.8.8) to Ubuntu 16.04 (svn
1.9.3), svnmucc commands started failing for me:
$ svnmucc --revision 0 --message 'test data, please ignore' -- put -
Sam Ruby wrote on Mon, 05 Jun 2017 10:08 -0400:
> When I moved whimsy from Ubuntu 14.04 (svn 1.8.8) to Ubuntu 16.04 (svn
> 1.9.3), svnmucc commands started failing for me:
>
> $ svnmucc --revision 0 --message 'test data, please ignore' -- put -
>
Thank you very much for the speedy change!
On Fri, May 2, 2014 at 10:54 PM, Ben Reser b...@reser.org wrote:
On 5/2/14, 3:24 PM, Dan Ellis wrote:
svnmucc currently only supports linefeed (LF, \n) line endings and
complains
about window's style carriage return, linefeed (CRLFs, \r\n) with:
On 5/2/14, 3:24 PM, Dan Ellis wrote:
svnmucc currently only supports linefeed (LF, \n) line endings and complains
about window's style carriage return, linefeed (CRLFs, \r\n) with:
Error: svnmucc: E125005: Cannot accept non-LF line endings in 'svn:log'
property
This is inconsistent with
Brother, unweaving the quotes is its own problem. You see, most
filesystems allow single quotes and double quotes in the filenames
themselves. Hilarity will ensue.
On Sun, Nov 17, 2013 at 4:19 AM, Vladislav Javadov vapaam...@yandex.ru wrote:
BZ The reason to support this syntax with command and
-Original Message-
From: Nico Kadel-Garcia [mailto:nka...@gmail.com]
Sent: Monday, November 18, 2013 7:12 AM
To: Vladislav Javadov
Cc: Blair Zajac; Andreas Mohr; Geoff Rowell; users@subversion.apache.org
Subject: Re: svnmucc
Brother, unweaving the quotes is its own problem. You
On Mon, 18 Nov 2013 07:11:40 +, Nico Kadel-Garcia wrote:
Brother, unweaving the quotes is its own problem. You see, most
filesystems allow single quotes and double quotes in the filenames
themselves. Hilarity will ensue.
Quoting is a solved problem, including quoting quotes.
Using
On Nov 18, 2013, at 7:33 AM, Andreas Krey a.k...@gmx.de wrote:
On Mon, 18 Nov 2013 07:11:40 +, Nico Kadel-Garcia wrote:
Brother, unweaving the quotes is its own problem. You see, most
filesystems allow single quotes and double quotes in the filenames
themselves. Hilarity will ensue.
Quoting is a solved problem, including quoting quotes.
Bwa-ha-ha-ha!. Hee. Giggle, Snort. Oh, dear lord, that one deserved a
coffee and cats warning. The handling of syntactically significant
characters, such as quotes, slashes, single quotes, and spaces is a
very common cross-platform problem
BZ The reason to support this syntax with command and arg on separate lines
BZ is to support files with whitespaces in the names
But what about quotes? Most OSes and programs accept quoted file names
containing spaces. Single-line commands are more readable, IMHO.
--
WBR,
Vladislav Javadov
On Nov 16, 2013, at 2:10 AM, Vladislav Javadov vapaam...@yandex.ru wrote:
rm programs/develop/fasm/tags
rm programs/games/mine/tags
rm programs/games/snake/tags
Each command argument must be on a separate line:
rm
programs/develop/fasm/tags
rm
programs/games/mine/tags
rm
On Sat, Nov 16, 2013 at 04:29:13AM -0500, Geoff Rowell wrote:
On Nov 16, 2013, at 2:10 AM, Vladislav Javadov vapaam...@yandex.ru wrote:
rm programs/develop/fasm/tags
rm programs/games/mine/tags
rm programs/games/snake/tags
Each command argument must be on a separate line:
rm
On 11/16/2013 03:06 AM, Andreas Mohr wrote:
On Sat, Nov 16, 2013 at 04:29:13AM -0500, Geoff Rowell wrote:
On Nov 16, 2013, at 2:10 AM, Vladislav Javadov vapaam...@yandex.ru wrote:
rm programs/develop/fasm/tags
rm programs/games/mine/tags
rm programs/games/snake/tags
Each command argument
On 11/16/13 8:38 AM, Blair Zajac wrote:
The reason to support this syntax with command and arg on separate lines is to
support files with whitespaces in the names, which wouldn't be possible wit
the
syntax of command and arg on a single line.
Yet another thing to add to the list of code that
On Fri, Jun 21, 2013 at 4:45 AM, Philip Martin
philip.mar...@wandisco.com wrote:
Nico Kadel-Garcia nka...@gmail.com writes:
# Compatibility symlink.
# This runs after the target of the same name in build-outputs.mk.
INSTALL_EXTRA_TOOLS=\
$(MKDIR) $(DESTDIR)$(bindir); \
test -n
Nico Kadel-Garcia nka...@gmail.com writes:
# Compatibility symlink.
# This runs after the target of the same name in build-outputs.mk.
INSTALL_EXTRA_TOOLS=\
$(MKDIR) $(DESTDIR)$(bindir); \
test -n $$SVN_SVNMUCC_IS_SVNSYITF \
ln -sf svnmucc$(EXEEXT)
34 matches
Mail list logo
