Accidentally dropped Mike and dev@community in my reply

-------- Original Message --------
Subject: Re: How was GSoC for you, and your students?
Date: Wed, 22 Aug 2012 17:41:47 +0200
From: Ulrich Stärk <u...@spielviel.de>
To: code-awa...@apache.org

Then update your working copy ;). ("Update this directory" at the top of the 
directory listing page)

Uli

On 22.08.2012 17:13, Michael McCandless wrote:
> On Wed, Aug 22, 2012 at 8:57 AM, Ross Gardler
> <rgard...@opendirective.com> wrote:
>> On 22 August 2012 13:33, Michael McCandless <luc...@mikemccandless.com> 
>> wrote:
>>> I installed the CMS bookmarklet, navigated to
>>> http://community.apache.org/mentoring/experiences.html, and then
>>> clicked it (the bookmarklet), but that redirects me to this URL:
>>>
>>>     https://cms.apache.org/community/wc/browse/mikemccand-voFLne/trunk
>>>
>>> (The top-level page for "community" ... and I can't find any
>>> "mentoring" subdir there).
>>
>> Interesting. When I click the bookmarklet on the experience page I go
>> to: 
>> https://cms.apache.org/community/wc/browse/rgardler-im0SBz/trunk/content/mentoring/experiences.mdtext
> 
> That makes sense (and what I expected!).
> 
>> I'd expect the first part to be different, but the trunk/content...
>> part should be the same
> 
> Right.
> 
>> (NB in checking this I spotted my type on
>> Lucene and fixed that).
> 
> Aha!  Thanks :)
> 
>> I note that a third person has succesfully edited the page (I
>> published this, thank you). So I don't think it's a problem with the
>> CMS.
> 
> Yeah.  It's really odd ... I can see the starting page, click into
> subdirs, etc., but I don't see a "mentoring" subdir.
> 
>> Can you try adding the [path from /trunk onwards to your URL)
> 
> I did that:
> 
>      
> https://cms.apache.org/community/wc/browse/mikemccand-voFLne/trunk/content/mentoring/experiences.mdtext
> 
> But I get a "Not Found" error.  So strange.  It's like I'm viewing and
> old version of the content from before "mentoring" was published ...
> 
> Mike McCandless
> 
> http://blog.mikemccandless.com
> 



Reply via email to