<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Recent Posts in Changesets Managed Manually | Unfuddle Community</title>
    <link>http://unfuddle.com/community</link>
    <description>Unfuddle Community Forums</description>
    <item>
      <guid isPermaLink="false">www.unfuddle.com/community:3:457:1440</guid>
      <title>Changesets Managed Manually replied by Brett Wilson @ Sat, 24 Jan 2009 21:42:58 UTC</title>
      <link>http://www.unfuddle.com/community/forums/3/topics/457</link>
      <description>Thank you for responding swiftly! Everything seems to be in order now and working well :)

Brett</description>
      <pubDate>Sat, 24 Jan 2009 21:42:58 UTC</pubDate>
      <author>Brett Wilson</author>
    </item>
    <item>
      <guid isPermaLink="false">www.unfuddle.com/community:3:457:1439</guid>
      <title>Changesets Managed Manually replied by David C. @ Sat, 24 Jan 2009 03:37:28 UTC</title>
      <link>http://www.unfuddle.com/community/forums/3/topics/457</link>
      <description>There was a bug, affecting a very small percentage of accounts, which was causing the check box to appear checked even if the option wasn't actually applied to that repository. Please note that this has now been fixed so the checkboxes show the correct (actual) selection. This also affected your repository causing it to not create changesets.

To answer your questions:

1) Yes, this is why there was no commit information visible in the source browser
2) Manually managing changesets is useful if you are not hosting your repository in Unfuddle but still want to track commits and associate them with tickets.
3) This bug was ignoring your preference. This has been fixed and you should now see information about your commits in the source browser. If you do not, please email us with your account subdomain and repository abbreviation and we will investigate.

I apologize for the confusion. Please let us know if you have any other questions.</description>
      <pubDate>Sat, 24 Jan 2009 03:37:28 UTC</pubDate>
      <author>David C.</author>
    </item>
    <item>
      <guid isPermaLink="false">www.unfuddle.com/community:3:457:1435</guid>
      <title>Changesets Managed Manually posted by Brett Wilson @ Fri, 23 Jan 2009 21:56:43 UTC</title>
      <link>http://www.unfuddle.com/community/forums/3/topics/457</link>
      <description>Alright this just seems a little odd to me. The svn server is not saving/sharing any information about who is committing changes. A little bit odd I thought, so I decided I would check out some of the repository properties. Well there is one option that was checked that I never checked. *Changesets Managed Manually*. I thought this was odd, so I unchecked it, saved the settings and went away for a bit. When I went back to the settings page it was STILL checked. I tried this several times, apparently it just ignores my choice (Bug?).

So I just have a couple quick questions.
1) Is this why there is no information about who made a commit when viewing the repository?
2) What does it mean to manage the changesets manually? I am just curious what this means for me as I am not doing anything with your API.
3) Is it actually ignoring my preference, or just appearing that way? 

I apologize if this was asked elsewhere, I did a quick search and couldn't find anything on it. Mostly I just wanted to mention the bug. Any information would be helpful. Thanks in advance!</description>
      <pubDate>Fri, 23 Jan 2009 21:56:43 UTC</pubDate>
      <author>Brett Wilson</author>
    </item>
  </channel>
</rss>

