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

Re: "svn list -v" column alignment issue

From: Branko ─îibej <brane_at_apache.org>
Date: Tue, 14 Jan 2020 13:19:08 +0100

On 13.01.2020 17:51, Daniel Shahaf wrote:
> Vincent Lefevre wrote on Mon, 13 Jan 2020 10:26 +00:00:
>> On 2020-01-10 16:58:26 +0100, Johan Corveleyn wrote:
>>> Since both 'svn ls -v' and 'svn blame' can be called on a repository
>>> URL, I don't really see the point in caching the max(length(author))
>>> of the working copy.
>>> The output from a URL would still be mis-aligned. It would make the
>>> presentation inconsistent between calling it on a working copy and on
>>> a URL.
>> Good point. I was about to say that in most cases, these commands are
>> run from a working copy. But I now think that caching should be done
>> under the user's home (just like with most applications). Under Unix,
>> this would be under "$XDG_CACHE_HOME/subversion".
> When would data be evicted from the cache?
>> The data should be associated with the URL of the repository.
> I'd say UUID, but we don't have to decide this now.

Why are we overthinking this? This information is really not relevant
for integration with other tools:

  * GUIs don't need it; they can always dynamically resize columns in forms.
  * The command-line doesn't (really) need it; all information,
    including untruncated commiter names, is available in --xml mode.

Adding a layer of caching is only going to add a stale-cache problem
that we don't have now.

-- Brane
Received on 2020-01-14 13:19:13 CET

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