Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "John B. Matthews" Newsgroups: comp.lang.java.programmer Subject: Re: Creating a subversion "tag change summary". Date: Mon, 16 Apr 2012 20:54:55 -0400 Organization: The Wasteland Lines: 39 Message-ID: References: NNTP-Posting-Host: LQJtZWzu+iKlBROuDg+IUg.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:13601 In article , Daniel Pitts wrote: > On 4/15/12 10:51 PM, John B. Matthews wrote: > > In article, > > Daniel Pitts wrote: > > > >> Well, I did find one way to speed things up. An "info" request > >> of the file on the tag is relatively fast, and includes the > >> "last change revision" of that file. I can then do a log of > >> that file on the trunk (Which is faster by magnitudes), and > >> anything after that revision can be considered a change after > >> that file was originally tagged. > >> > >> Anyway, I'm still open to any other advice on the matter. > > > > This reminds me of a project that had a particularly tangled > > per-directory access control configuration. You might look at > > the speed versus security tradeoff in "Disabling path-based > > checks." > > > I'm not sure I understand what you mean by that, but that does > remind me that our admins have prevented checkouts that don't > have "/branches/*/", "/tags/*/" or "/trunk/" in them. Not sure if > that is contributing to the problem or not. I'm not sure how they're enforcing it, but "Per-directory access control" is one way, and "Disabling path-based checks" is one alternative, both discussed here: A symptom is that the time required to obtain older `info` increases (roughly) geometrically with age. -- John B. Matthews trashgod at gmail dot com