[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r1825045 - /subversion/trunk/subversion/svn/svn.c

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 24 Mar 2018 20:02:45 +0000

julianfoad_at_apache.org wrote on Thu, 22 Feb 2018 11:02 +0000:
> +++ subversion/trunk/subversion/svn/svn.c Thu Feb 22 11:02:02 2018
> @@ -1831,7 +1831,7 @@ const svn_opt_subcommand_desc2_t svn_cl_
> "\n"
> " To bring back a shelved change, use 'svn unshelve NAME'.\n"
> "\n"
> - " A shelved change is stored as a patch file, .svn/shelves/NAME.patch\n"
> + " Shelved changes are stored in <WC>/.svn/shelves/\n"

I noticed this line while reviewing the backport and wanted to ask, why
do we document the storage location publicly? We don't generally
promise anything about the internal structure of .svn/ so this would
be a first.

Cheers,

Daniel

> "\n"
> " The shelving feature is EXPERIMENTAL. This command is likely to change\n"
> " in the next release, and there is no promise of backward compatibility.\n"
Received on 2018-03-24 21:02:49 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.