<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: About</title>
	<atom:link href="http://www.stum.de/about/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stum.de</link>
	<description>Random thoughts of neat disorder</description>
	<lastBuildDate>Wed, 11 Jan 2012 04:38:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Just old 64 geezer</title>
		<link>http://www.stum.de/about/comment-page-1/#comment-67254</link>
		<dc:creator>Just old 64 geezer</dc:creator>
		<pubDate>Fri, 02 Dec 2011 14:21:18 +0000</pubDate>
		<guid isPermaLink="false">#comment-67254</guid>
		<description>I noticed your c64 related question in certain site (stackxchange)... If you want to know more c64 stuff, mem things for it etc., feel free to email me and I answer what ever I can... Kinda curious here what kinda &quot;game&quot; you might be up to... I used to do c64 stuff (since i was kid) from like 1984 to mid 90&#039;s (and now and then later) so I prolly can answer some of your questions...</description>
		<content:encoded><![CDATA[<p>I noticed your c64 related question in certain site (stackxchange)... If you want to know more c64 stuff, mem things for it etc., feel free to email me and I answer what ever I can... Kinda curious here what kinda "game" you might be up to... I used to do c64 stuff (since i was kid) from like 1984 to mid 90's (and now and then later) so I prolly can answer some of your questions...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jörg Loebnau</title>
		<link>http://www.stum.de/about/comment-page-1/#comment-64855</link>
		<dc:creator>Jörg Loebnau</dc:creator>
		<pubDate>Fri, 18 Nov 2011 11:03:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-64855</guid>
		<description>Hi there,

Does anyone know how to use cmdsendmail with non-English characters? After regular sending failed, I tried to decode Umlauts etc. using HTML (ä	as &#228; etc.) but I only got an error message:


cmdsendmail Deutsch.xml
CommandLine Send Mail 1.0.5 · http://www.Stum.de
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

ERROR: File Deutsch.xml is invalid!
Message: Reference to undeclared entity &#039;Uuml&#039;. Line 14, position 19.

Finished execution on 2011-11-18 11:55:51



What could I do here?
Thanks in advance,

Jörg</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>Does anyone know how to use cmdsendmail with non-English characters? After regular sending failed, I tried to decode Umlauts etc. using HTML (ä	as &auml; etc.) but I only got an error message:</p>
<p>cmdsendmail Deutsch.xml<br />
CommandLine Send Mail 1.0.5 · <a href="http://www.Stum.de" rel="nofollow">http://www.Stum.de</a><br />
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯</p>
<p>ERROR: File Deutsch.xml is invalid!<br />
Message: Reference to undeclared entity 'Uuml'. Line 14, position 19.</p>
<p>Finished execution on 2011-11-18 11:55:51</p>
<p>What could I do here?<br />
Thanks in advance,</p>
<p>Jörg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mstum</title>
		<link>http://www.stum.de/about/comment-page-1/#comment-382</link>
		<dc:creator>mstum</dc:creator>
		<pubDate>Tue, 08 Jul 2008 18:18:39 +0000</pubDate>
		<guid isPermaLink="false">#comment-382</guid>
		<description>Hi,

thanks for the comment!
I don&#039;t have the exact Syntax handy right now, but you can work with the LimitExcept block.
Repo3 is the easiest, as the first example (the one with  Require valid-user) will allow every user to do stuff.

For repo2, i _guess_ that something like
&lt;Location /repo2&gt;
DAV svn
SVNPath c:\repos\repo2
AuthType Basic
AuthName &quot;Subversion Repository&quot;
AuthUserFile c:\svn-user-file
Require user user1 user2
&lt;/Location&gt;

should do the trick: user1 and user2 can connect and do stuff, wheras user3 cannot access this at all.

Repo1 is a bit more tricky. Again, i guess that something like
&lt;Location /svn/repo1&gt;
DAV svn
SVNPath c:\repos\repo1
AuthType Basic
AuthName &quot;Subversion Repository&quot;
AuthUserFile c:\svn-user-file
&lt;Limit GET PROPFIND OPTIONS REPORT&gt;
Require user user3
&lt;/Limit&gt;
&lt;LimitExcept GET PROPFIND OPTIONS REPORT&gt;
Require user user1 user2
&lt;/LimitExcept&gt;
&lt;/Location&gt;

could work, but i have not tested it. (Maybe user1 and user2 also need to be in the Limit-block or simply put require valid-user in there)
Have a look at the documentation for Apache:
http://httpd.apache.org/docs/2.2/mod/core.html#limit

I&#039;ll try to research some stuff a bit later (kinda busy at the moment) and create a follow up post on the various Options to allow finer-granulation.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>thanks for the comment!<br />
I don't have the exact Syntax handy right now, but you can work with the LimitExcept block.<br />
Repo3 is the easiest, as the first example (the one with  Require valid-user) will allow every user to do stuff.</p>
<p>For repo2, i _guess_ that something like<br />
&lt;Location /repo2&gt;<br />
DAV svn<br />
SVNPath c:\repos\repo2<br />
AuthType Basic<br />
AuthName "Subversion Repository"<br />
AuthUserFile c:\svn-user-file<br />
Require user user1 user2<br />
&lt;/Location&gt;</p>
<p>should do the trick: user1 and user2 can connect and do stuff, wheras user3 cannot access this at all.</p>
<p>Repo1 is a bit more tricky. Again, i guess that something like<br />
&lt;Location /svn/repo1&gt;<br />
DAV svn<br />
SVNPath c:\repos\repo1<br />
AuthType Basic<br />
AuthName "Subversion Repository"<br />
AuthUserFile c:\svn-user-file<br />
&lt;Limit GET PROPFIND OPTIONS REPORT&gt;<br />
Require user user3<br />
&lt;/Limit&gt;<br />
&lt;LimitExcept GET PROPFIND OPTIONS REPORT&gt;<br />
Require user user1 user2<br />
&lt;/LimitExcept&gt;<br />
&lt;/Location&gt;</p>
<p>could work, but i have not tested it. (Maybe user1 and user2 also need to be in the Limit-block or simply put require valid-user in there)<br />
Have a look at the documentation for Apache:<br />
<a href="http://httpd.apache.org/docs/2.2/mod/core.html#limit" rel="nofollow">http://httpd.apache.org/docs/2.2/mod/core.html#limit</a></p>
<p>I'll try to research some stuff a bit later (kinda busy at the moment) and create a follow up post on the various Options to allow finer-granulation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.stum.de/about/comment-page-1/#comment-380</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Tue, 08 Jul 2008 16:28:35 +0000</pubDate>
		<guid isPermaLink="false">#comment-380</guid>
		<description>I read your blog over subversion and it was very helpful on getting me running...  I am however running into one issue and wanted to ask for your advice.  I read the second part of your suberversion blog (over multiple repos) and wanted to do something similar to what you are doing (1 auth file with multiple repos) but I am not sure how to keep someone (userx) out of a particular repo completely (I do not want them even having read access)...

i.e,

Repo1, 2 and 3 - User1, 2 and 3

Repo1 only can be accessed (read and write) by User 1,2 but 3 can read
Repo2 only can be accessed by 1 and 2 (3 can&#039;t even read)
Repo 3 can be accessed by all with full permissions..

Does any of this make sense!    Do you recommend me doing anything here?   I am lost and can&#039;t find anything in my searches, only similar examples like in your blog.  Not a complete block in the repo for any given user...

BTW: I do like the skating - seems very cool, also checked your video on google - looks like a great time!

Respectfully,
Kevin Wilson</description>
		<content:encoded><![CDATA[<p>I read your blog over subversion and it was very helpful on getting me running...  I am however running into one issue and wanted to ask for your advice.  I read the second part of your suberversion blog (over multiple repos) and wanted to do something similar to what you are doing (1 auth file with multiple repos) but I am not sure how to keep someone (userx) out of a particular repo completely (I do not want them even having read access)...</p>
<p>i.e,</p>
<p>Repo1, 2 and 3 - User1, 2 and 3</p>
<p>Repo1 only can be accessed (read and write) by User 1,2 but 3 can read<br />
Repo2 only can be accessed by 1 and 2 (3 can't even read)<br />
Repo 3 can be accessed by all with full permissions..</p>
<p>Does any of this make sense!    Do you recommend me doing anything here?   I am lost and can't find anything in my searches, only similar examples like in your blog.  Not a complete block in the repo for any given user...</p>
<p>BTW: I do like the skating - seems very cool, also checked your video on google - looks like a great time!</p>
<p>Respectfully,<br />
Kevin Wilson</p>
]]></content:encoded>
	</item>
</channel>
</rss>

