Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 6 Mar 2017 16:10:32 +0000
From: Daniel Shahaf <danielsh@apache.org>
To: dev@subversion.apache.org
Cc: Doug Robinson <doug.robinson@wandisco.com>
Subject: 'svn lock -q' (was: Suspected issue with "remove-zombie-locks.py"?)
Message-ID: <20170306161032.GA5041@fujitsu.shahaf.local2>
References: <CALq3gdMG5kpLSC=+mJUsrU16DB87v6ZJNBJujQeLJd-uEBRUXw@mail.gmail.com>
 <CALq3gdOTiXYVv_oCXg9CO8nKEEo2e4PtsKPth-xqDKnbUmJL4A@mail.gmail.com>
 <20170306160644.GA4755@fujitsu.shahaf.local2>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20170306160644.GA4755@fujitsu.shahaf.local2>
User-Agent: Mutt/1.5.23 (2014-03-12)
archived-at: Mon, 06 Mar 2017 16:15:22 -0000

Daniel Shahaf wrote on Mon, Mar 06, 2017 at 16:06:44 +0000:
> I can reproduce this using the FS API only (without the contrib/ script):

While reproducing this I ran into:

    % svn lock -q a
    Subcommand 'lock' doesn't accept option '-q [--quiet]'
    Type 'svn help lock' for usage.

I assume the following will fix it, but I don't have a build environment
so I can't test it.

[[[
Index: subversion/svn/svn.c
===================================================================
--- subversion/svn/svn.c	(revision 1785678)
+++ subversion/svn/svn.c	(working copy)
@@ -807,7 +807,7 @@ const svn_opt_subcommand_desc2_t svn_cl__cmd_table
      "usage: lock TARGET...\n"
      "\n"
      "  Use --force to steal the lock from another user or working copy.\n"),
-    { opt_targets, 'm', 'F', opt_force_log, opt_encoding, opt_force },
+    { opt_targets, 'q', 'm', 'F', opt_force_log, opt_encoding, opt_force },
     {{'F', N_("read lock comment from file ARG")},
      {'m', N_("specify lock comment ARG")},
      {opt_force_log, N_("force validity of lock comment source")}} },
]]]

Cheers,

Daniel