<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="./" rel="self" type="application/rss+xml" />
    <title>Latest ditz updates for ditz</title>
    <link>index.html</link>
    <description>Latest updates to the distributed issue tracker for ditz</description>
    <language>en-us</language>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; closed with disposition fixed can we render the spanish n ñ</title> 
      <link>issue-3da0b9b5cb59a720849a9cc5b35da51d150606e3.html</link>
      <description>we can!</description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; closed with disposition fixed Issue fields in UTF-8 encoding are stored in uneditable format</title> 
      <link>issue-9a617371b887e759c9aa3bf9c4deb8a63f8260df.html</link>
      <description>fixed by change to yaml-waml</description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; assigned to release 0.6 from unassigned Issue fields in UTF-8 encoding are stored in uneditable format</title> 
      <link>issue-9a617371b887e759c9aa3bf9c4deb8a63f8260df.html</link>
      <description></description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; closed with disposition fixed Тестовая бага, для проверки поддержки UTF8</title> 
      <link>issue-422d53615d2d3a5318cf38f9c7837c6abb83cbc0.html</link>
      <description></description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; assigned to release 0.6 from unassigned Тестовая бага, для проверки поддержки UTF8</title> 
      <link>issue-422d53615d2d3a5318cf38f9c7837c6abb83cbc0.html</link>
      <description>looks like this is fixed in 0.6</description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; created can we render the spanish n ñ</title> 
      <link>issue-3da0b9b5cb59a720849a9cc5b35da51d150606e3.html</link>
      <description></description>
      <pubDate>2011-03-17</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; created Fix the changelog</title> 
      <link>issue-3fbb97572f3745a8cf791f0a177e6302c2354c86.html</link>
      <description></description>
      <pubDate>2011-03-16</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; assigned to release 0.6 from unassigned rss feed for recent activity</title> 
      <link>issue-f2afaf28ea57273e132226139b7f98e9579b236d.html</link>
      <description>it will go in the next release</description>
      <pubDate>2011-03-15</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; closed with disposition fixed rss feed for recent activity</title> 
      <link>issue-f2afaf28ea57273e132226139b7f98e9579b236d.html</link>
      <description>we have a new template feed.rhtml that gets generated every time ditz html is run

Still not very clever in specifiying things like LINK item etc because we can't give fully qualified urls</description>
      <pubDate>2011-01-30</pubDate>
    </item>
  
    <item>
      <title>Matt Katz &lt;ditz@morelightmorelight.com&gt; issue claimed rss feed for recent activity</title> 
      <link>issue-f2afaf28ea57273e132226139b7f98e9579b236d.html</link>
      <description>claiming rss of recent activity</description>
      <pubDate>2011-01-30</pubDate>
    </item>
  
    <item>
      <title>Andrei Dziahel &lt;develop7@develop7.info&gt; created Issue fields in UTF-8 encoding are stored in uneditable format</title> 
      <link>issue-9a617371b887e759c9aa3bf9c4deb8a63f8260df.html</link>
      <description></description>
      <pubDate>2010-09-28</pubDate>
    </item>
  
    <item>
      <title>Andrei Dziahel &lt;develop7@develop7.info&gt; created Тестовая бага, для проверки поддержки UTF8</title> 
      <link>issue-422d53615d2d3a5318cf38f9c7837c6abb83cbc0.html</link>
      <description>Комментарий к тестовой баге</description>
      <pubDate>2010-09-28</pubDate>
    </item>
  
    <item>
      <title>Travis Parker &lt;travis.parker@gmail.com&gt; created empty description from editor kills ditz</title> 
      <link>issue-046c98d6ba5ac3c5fc2d18e1836f3604a012e0e9.html</link>
      <description></description>
      <pubDate>2009-07-12</pubDate>
    </item>
  
    <item>
      <title>Travis Parker &lt;travis.parker@gmail.com&gt; closed with disposition fixed support tiny issue identifiers (like #34) in the single-component case</title> 
      <link>issue-2cd9e99ca6ca316f37262022b4277913fd23eae0.html</link>
      <description>if there is only one component, canonically use the short version and translate
long versions to short ones in the argument-parsing code</description>
      <pubDate>2009-07-08</pubDate>
    </item>
  
    <item>
      <title>Travis Parker &lt;travis.parker@gmail.com&gt; closed with disposition fixed .ditz-plugins file should be optional</title> 
      <link>issue-4d05c780343b3ab02755132463c592076aa2f6c8.html</link>
      <description>add 'if File.exists? pluginfile' to bin/ditz, mirroring sheila/sheila.rb</description>
      <pubDate>2009-07-08</pubDate>
    </item>
  
    <item>
      <title>Travis Parker &lt;travis.parker@gmail.com&gt; created .ditz-plugins file should be optional</title> 
      <link>issue-4d05c780343b3ab02755132463c592076aa2f6c8.html</link>
      <description></description>
      <pubDate>2009-07-08</pubDate>
    </item>
  
    <item>
      <title>Daniel Kalør &lt;daniel@kalor.dk&gt; created shell completion and plugins</title> 
      <link>issue-124366a44d339a0e4c200948d5a8a8eec90f1eef.html</link>
      <description>Created via Sheila by  (82.211.215.253)</description>
      <pubDate>2008-11-11</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; created issue-claiming plugin should compare email addresses only</title> 
      <link>issue-3aaa22f6ec646eb6c90f32808ff15dae13db1efc.html</link>
      <description></description>
      <pubDate>2008-11-10</pubDate>
    </item>
  
    <item>
      <title>Matt Wilson &lt;matt@tplus1.com&gt; commented markdown/textile/redcloth support in descriptions and comments</title> 
      <link>issue-53310ae2fbdfb553eb9189c3e33c07911289e6c5.html</link>
      <description>Actually, never mind.  As long as when the textile is rendered, it's pulled out and adjusted, then it can be safely stored.

I think maybe ditz edit might be better if it broke the issue into components, and then opened each in a temp.  Or maybe there could be a ditz edit-description that just does that.

(submitted via Sheila by 99.161.134.95 ())</description>
      <pubDate>2008-11-08</pubDate>
    </item>
  
    <item>
      <title>Matt Wilson &lt;matt@tplus1.com&gt; commented markdown/textile/redcloth support in descriptions and comments</title> 
      <link>issue-53310ae2fbdfb553eb9189c3e33c07911289e6c5.html</link>
      <description>I'm not very familiar with yaml, but it seems like yaml requires that the text for the description field, for example, starts indented two characters in.

So, if yaml requires that indentation, then that might not play nice with some of these markup systems that depend on being in the first character in the line.

If this is true, what about storing the description text in a separate file, and in the yaml, just storing the path to that file?



(submitted via Sheila by 99.161.134.95 ())</description>
      <pubDate>2008-11-08</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; closed with disposition fixed add configuration setting for controlling pager invocation</title> 
      <link>issue-50c68d6ebd81149d12fc44e311792a3418f2e687.html</link>
      <description></description>
      <pubDate>2008-11-07</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; commented comments should be in separate files, like issues are</title> 
      <link>issue-738933ad98319fa510a8fe02176902378e5df6f0.html</link>
      <description>maybe revisit sheila-1 once this is done.</description>
      <pubDate>2008-11-06</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; commented check for a "git push" having updated the issue db, and reload if so</title> 
      <link>issue-febe451f6bbd6525353d737afb1114d6c8261025.html</link>
      <description>maybe once ditz-78 is done, it will make sense to revisit this.</description>
      <pubDate>2008-11-06</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; commented releases and components should be separate files, like issues are</title> 
      <link>issue-80c023565e81acb7ad0ee4c41ebe894dac4ba743.html</link>
      <description>also see ditz-78, a sister issue.</description>
      <pubDate>2008-11-06</pubDate>
    </item>
  
    <item>
      <title>William Morgan &lt;wmorgan-ditz@masanjin.net&gt; created comments should be in separate files, like issues are</title> 
      <link>issue-738933ad98319fa510a8fe02176902378e5df6f0.html</link>
      <description></description>
      <pubDate>2008-11-06</pubDate>
    </item>
  
  </channel>
</rss>
