On Fri, Jan 22, 2010 at 3:18 PM, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> Stefan Sperling wrote:
>> On Thu, Jan 21, 2010 at 07:06:07PM +0000, Julian Foad wrote:
>> > In light of that, do you think it would be better to ship
>> > the current (trunk) version of that file each time we make a release?
>>
>> If Hyrum can do this without major hassle, +1.
>
> I discovered a surprise. My colleague's actual concern turns out to be
> that
>
> google(subversion committers)
>
> returned the 1.4.x version. When I try it, sure enough, I get:
>
> <http://svn.apache.org/repos/asf/subversion/branches/1.4.x/COMMITTERS>
>
> as its first hit, and then some other kinds of pages, and then at number
> 5 is the trunk version in the OLD repository:
>
> <http://svn.collab.net/repos/svn/trunk/COMMITTERS>
>
> and NO OTHER copies of that file in the first several pages of results,
> that I can see.
>
> Now that's not our fault, and we are certainly not in the business of
> tweaking our search engine results, but it would be good if we could do
> something to reduce the obsolescence of information found in this
> manner. Can I back-port the updates just to accommodate this quirk
> because it has a real practical benefit, even though technically
> speaking it's a stupid thing?
>
Posting actual list of commiters somewhere on web site will solve this
problem since it will have much better PageRank than COMMITERS file
somewhere in repository. Also this saves us from rewriting our
history.
--
Ivan Zhakov
VisualSVN Team
Received on 2010-01-22 13:26:44 CET