<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.version-control.darcs.user">
    <title>gmane.comp.version-control.darcs.user</title>
    <link>http://blog.gmane.org/gmane.comp.version-control.darcs.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26406"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26404"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26401"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26395"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26392"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26391"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26390"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26387"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26386"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26378"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26377"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26367"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26365"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26362"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26357"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26339"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26336"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26329"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26327"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26326"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26406">
    <title>Conventions on teams using darcs - naming, patch size,etc.</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26406</link>
    <description>&lt;pre&gt;
Are there any conventions that users tend to gravitate towards?

1.  Naming - with patches from a lot of people, do short names like : 
"Fixed the serialization of Foo" work?  Do long names wrap a line
telling exactly what you did work better?  Or do you fall back on bug
numbers?  What if you can't fall back on issue numbers?  Does
pinpointing a patch by name or in some context get tricky?
2.  Change granularity - do people tend to try to split a change up into
parts, e.g. if a library and end-code are in the same repo, maybe patch
the lib first and then the rest adding it as a dependency?
3.  Merging patches. . .  Does pollution of lots of tiny little changes
ever become a problem, or something you address in practice?  For
example, say people all work on some related issue, put in lots of
little fixes, then you're done - is it ever something where you want to
just merge them all and have everyone work in terms of the amended
repository?  Or does the UI/history/etc. make it easy to find, or not
find if you don't want the clutter, the aggregate of compound changes?

Any ideas, thoughts, experience on how people tend to handle long-lived
group projects, with Darcs, appreciated.
&lt;/pre&gt;</description>
    <dc:creator>Matt Lamari</dc:creator>
    <dc:date>2012-05-23T00:36:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26404">
    <title>optimization in HEAD: darcs diff</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26404</link>
    <description>&lt;pre&gt;I'd like to share to the darcs-users list another significant change
in HEAD that happened after the release of Darcs 2.8, this time an
optimization.

In 2010 Petr Rockai optimized the "darcs diff" command, but a few
things blocked the inclusion of this piece of code into darcs.
Notably, the optimization did not support old-fashioned repositories.
However, since version 2.8 Darcs no longer fully support these
repositories, so the new implementation of "diff" has been ported to
HEAD.

As in Petr's words (http://bugs.darcs.net/patch351):

----8&amp;lt;----
I have changed the diff code to only write those files that actually changed in
the temporary locations. On my other project (less than 1000 working copy
files):

(with cold cache)
head: darcs diff  1,09s user 0,58s system 9% cpu 16,752 total
now:  darcs diff  0,14s user 0,04s system 6% cpu 2,978 total

(with hot cache)
head: darcs diff  0,36s user 0,18s system 98% cpu 0,548 total
now:  darcs diff  0,06s user 0,01s system 86% cpu 0,078 total
----&amp;gt;8----

I've added more informal benchmarks at the end of this mail.

So, if you want to build a darcs from HEAD and discover again "darcs
diff", have a go at it and see how fast it has become!
If you are using an external diffing tool, you can use the new flag
--no-pause-for-gui (http://bugs.darcs.net/patch748) implemented by
Michael Hendricks.

Following the switch to this new implementation, Owen Stephens noticed
that diffing directories no longer worked
(http://bugs.darcs.net/issue2179) but Yuriy Vostrikov soon sent a
patch fixing this issue (http://bugs.darcs.net/patch818).

If you find more bugs, please let us know!

Guillaume

&lt;/pre&gt;</description>
    <dc:creator>Guillaume Hoffmann</dc:creator>
    <dc:date>2012-05-21T19:59:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26401">
    <title>Darcs really needs a book</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26401</link>
    <description>&lt;pre&gt;
I think that the subject matter really warrants a handy paperback.
&lt;/pre&gt;</description>
    <dc:creator>Matt Lamari</dc:creator>
    <dc:date>2012-05-20T20:17:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26395">
    <title>How to separate some files from a repository</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26395</link>
    <description>&lt;pre&gt;Hi,

I began a project about six months ago as a single repository. I've
now reached the point where I'd like to split out several files into a
separate library, for use across multiple projects. Of course, I also
want to preserve the history of these files in the new library
repository. However, several of these patches include changes to other
files (eg, in response to changes in module interfaces) and in order
to pull all of the library-specific patches, I end up having to pull
in a large number of additional patches. What I'd like to do is
identify the relevant patches ("darcs changes file1 ... fileN") and
pull modified versions of these patches that do not include any hunks
that modify other files in the repository.

I can't see a more efficient way of doing this than manually applying
and recording individual hunks (using "darcs changes -v file1 ...
fileN", or "darcs annotate --match XXX" and "darcs unrecord --last 1
--matches XXX"). It sounds as though the "amend-record on steroids"
feature would be useful here. Is there another way to achieve (with
darcs 2.8.1) what I'm trying to accomplish?

Thanks for any advice,
Rob
&lt;/pre&gt;</description>
    <dc:creator>Rob Moss</dc:creator>
    <dc:date>2012-05-17T10:53:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26392">
    <title>welcome Simon Michael to the Darcs team</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26392</link>
    <description>&lt;pre&gt;Hi all,

Just announcing another newcomer to the Darcs team.

Simon Michael recently put a lot of work into revamping the Darcs homepage.
As part of the team, he will be working primarily on the page and documentation, and hopefully over time, expand his areas of interest.

Thanks,

&lt;/pre&gt;</description>
    <dc:creator>Eric Kow</dc:creator>
    <dc:date>2012-05-14T18:38:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26391">
    <title>darcs weekly news #96</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26391</link>
    <description>&lt;pre&gt;# News and discussions

1.  Darcs 2.8.1 was released, the only change is a build dependency that
    will make it buildable with the next Haskell Platform:

    -   http://lists.osuosl.org/pipermail/darcs-users/2012-May/026506.html
    -   http://hackage.haskell.org/package/darcs-2.8.1

2.  Meanwhile in HEAD, a new test strategy has been implemented:

    -   http://lists.osuosl.org/pipermail/darcs-users/2012-May/026503.html

3.  On the developers' mailing list, we are discussing how to make the
    darcs development process more friendly:

    -    http://lists.osuosl.org/pipermail/darcs-devel/2012-May/013820.html

# Issues resolved in the last week (3)

issue1921 Owen Stephens
  ~ -   return Nothing in splitOnTag if the tag isn't in the patchset
    -   http://bugs.darcs.net/issue1921

issue2095 Ganesh Sittampalam
  ~ -   avoid new GHC encoding behaviour using a global setting
    -   http://bugs.darcs.net/issue2095

issue2161 Owen Stephens
  ~ -   - don't use a separate type-variable for recorded/tentative in WhatsNew
    -   http://bugs.darcs.net/issue2161


# Patches applied in the last week (77)

2012-05-14 Simon Michael
  ~ -   home page: 2.8.1 release, trim news

2012-04-01 Ganesh Sittampalam
  ~ -   enable issue1763 test on Windows as it seems to work
    -   resolve conflicts in GHC encodings fix
    -   resolve issue2095: avoid new GHC encoding behaviour using a
global setting
    -   resolve conflict between issue2161 fix and witness macro removal

2012-03-21 Owen Stephens
  ~ -   resolve issue2161 - don't use a separate type-variable for
recorded/tentative in WhatsNew

2012-05-12 Simon Michael
  ~ -   home page: link hosting sites as suggested by Radoslav Dorcik

2012-04-21 Marc Simpson
  ~ -   Add new 'usageInfo' implementation (Darcs.Usage); employ in
Darcs.Command.

2012-05-12 Guillaume Hoffmann
  ~ -   Accept issue2138 whatsnew --summary not reporting conflicts
    -   fix duplicate appearance of darcs test in manual
    -   fix failing test for issue2100
    -   make exit code of darcs add non-zero if any adds fail

2012-01-19 Ganesh Sittampalam
  ~ -   resolve conflict in version number
    -   TAG 2.9.1
    -   bump version to 2.9.1

2011-09-07 Eric Kow
  ~ -   Accept issue2100: darcs add should move on from first failure.

2012-05-10 Simon Michael
  ~ -   home page: trim news
    -   home page: update news
    -   site: more css color cleanup
    -   home page: or tweak
    -   site: border color fix
    -   site: css cleanups, pre bottom border
    -   home page: move or
    -   site: underline links only on hover
    -   update Summersault thanks per markstos
    -   home page: box shadow for examples, add the dark bg style but
don't use it
    -   home page: less top padding, splash fits on iphone screen
    -   home page: download box shadow

2012-04-11 Owen Stephens
  ~ -   Use a couple of &amp;lt; at &amp;gt;-patterns in Patch.Depends
    -   Rename getTagsRight -&amp;gt; getUncovered, and move helpers into where block.
    -   More tweaking of haddock of splitOnTag in Patch.Depends
    -   Change name of infoAndDeps and add haddock to better express intent
    -   Tweak/add more haddock to Patch.Depends
    -   Reduce some duplication and tweak identifier names in Patch.Depends
    -   Rename eatOne -&amp;gt; unwrapOneTagged and extract common code in
Patch.Depends
    -   Tidy up and style changes for Exec
    -   Indentation and line-wrapping in English
    -   Add some Haddock and tweak some identifier names in Patch.Depends
    -   Fixup a couple of occurences of with_partial_intersection in
Patch.Depends
    -   Resolve issue1921: return Nothing in splitOnTag if the tag
isn't in the patchset
    -   Tweak issue1921 test to check for graceful failure
    -   Tweak a few identifiers and implementation of helpers for getTagsRight
    -   Remove unused getPatchesInTag function from Patch.Depends
    -   Rename and refactor simpleTag in Patch.Depends, to better express intent
    -   A few more operator spacing tidy-ups in Patch.Depends
    -   Accept issue1921: attempting to apply a patch bundle based on
missing tag dies.
    -   Tidy/style Patch.Depends

2012-05-11 Michael Hendricks
  ~ -   Fix utf8 test for rollback --no-record default

2012-04-29 Florent Becker
  ~ -   Tweak rollback help
    -   Give feedback when no hunks are selected in rollback --no-record
    -   Change rollback help to reflect --no-record as the default
    -   Make rollback --no-record the default

2012-05-05 Yuriy Vostrikov
  ~ -   Fix "darcs diff" handling of directory argument.

2012-05-04 Michael Hendricks
  ~ -   Accept Bitcoin donations via CoinCard

2012-04-01 Florent Becker
  ~ -   Make findUncommon and findCommonWithThem into findCommonAndUncommon
    -   More precise witnesses for with_partial_intersection
    -   in with_partial_intersection, we only need to assert that the
middle witness (wA) is correct

2012-03-30 Owen Stephens
  ~ -   Add failing test for issue2047.

2012-05-02 Simon Michael
  ~ -   home page: browsable darcs repo renamed to darcs-screened
    -   home page: anchor fix
    -   home page: drop "The" from the sidelinks
    -   home page: donate link in the footer
    -   home page: more linkage, wording tweaks
    -   stylesheet indentation
    -   shrink h1 font a tad
    -   home page: fix confusing comment
    -   home page: wording
    -   home page: merge two example sections
    -   home page: try more linkage in quick start intro
    -   home page: polish
    -   home page: wording
    -   home page polish
    -   home page clarifications, incorporate Florent Becker's feedback
    -   home page: wasteful but stylish whitespace, we're scrolling anyway
    -   Smart -&amp;gt; Simple in slogan
    -   new home page layout and content

2012-03-15 Owen Stephens
  ~ -   Changes --xml would incorrectly report the originating patch
of a given filename (in the case of renames)
&lt;/pre&gt;</description>
    <dc:creator>Guillaume Hoffmann</dc:creator>
    <dc:date>2012-05-14T18:49:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26390">
    <title>darcs 2.8.1 release</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26390</link>
    <description>&lt;pre&gt;Hi,

I've just released darcs 2.8.1 to hackage. The only change it
incorporates is a bump to the dependency on mtl to allow it to build
against the upcoming Haskell Platform.

Therefore there's no need for any users to upgrade, nor is there any
particular need for updated binaries except perhaps to avoid confusion
about binaries being out of date.

Cheers,

Ganesh
&lt;/pre&gt;</description>
    <dc:creator>Ganesh Sittampalam</dc:creator>
    <dc:date>2012-05-14T18:17:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26387">
    <title>Please upgrade your hackage package to mtl-2.1</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26387</link>
    <description>&lt;pre&gt;Dear Hackage package maintainer,

the release of the next haskell-platform is close, and it will most
likely ship with mtl-2.1.1. Your package on Hackage does not allow
building against this version, which makes it for your users and
distribution packagers difficult to use the package. Please consider
uploading a new version of your package with an extended mtl (and
possibly transformers) dependency range. In most cases, no version
changes are required.

The list of affected packages¹ are:
darcs
diagrams-cairo
ghc-events 
haskeline
leksah
ltk
template
vty
haskelldb
rss2irc

The current plan for package versions in the platform can be seen at
https://github.com/haskell/haskell-platform/blob/pre-release/haskell-platform.cabal


Thanks,
Joachim

¹ Only listing packages that are also shipped by Debian, not all
affected packages on Hackage.

&lt;/pre&gt;</description>
    <dc:creator>Joachim Breitner</dc:creator>
    <dc:date>2012-05-13T11:02:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26386">
    <title>new feature in HEAD: exponential backoff test strategy</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26386</link>
    <description>&lt;pre&gt;Hi everyone,

First, for those who have missed it, since darcs 2.8 all code testing
features of darcs belong to the command "darcs test". Without flags,
"darcs test" runs a test on the latest recorded state of the
repository. However, flags --trackdown and --bisect look for the most
recent recorded version passing a given test.

We already know how --trackdown  and --bisect work: --trackdown runs a
test agains the last recorded version, then the last version minus one
patch, then minus two patches... until finding a passing test.
--bisect sort of does the same by jumping back and forth in the
history by dichotomy.  See http://wiki.darcs.net/Using/Trackdown for
more information and unusually friendly drawings :-)

So, the new interesting feature in HEAD is the exponential backoff
strategy, implemented by Michael Hendricks.  As explained by Michael
himself on the bug tracker:

----8&amp;lt;----
This patch series defines a new "darcs test" search strategy named
--backoff.  It's aimed at finding regressions which are closer to the
head than to the middle of the repository.  Under these conditions, in
the screened repository, it performs between 30 and 70% faster than
bisect.  It will perform relatively better on repositories with more
patches.

The search strategy starts by unapplying 4 patches (chosen to match
the break-even point with linear search).  If the test fails, it
unapplies 8 more patches and tests again.  On each test failure, it
removes twice the number of patches as before.  Once the test passes,
it bisects the patches it just skipped.
----&amp;gt;8----

I think it's quite cool, and I'm not aware of any other VCS that have
this kind of test strategy.

Guillaume
&lt;/pre&gt;</description>
    <dc:creator>Guillaume Hoffmann</dc:creator>
    <dc:date>2012-05-12T23:03:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26378">
    <title>darcs weekly news #95</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26378</link>
    <description>&lt;pre&gt;# News and discussions

1.  Darcs 2.8 was released:

    -   http://lists.osuosl.org/pipermail/darcs-users/2012-April/026493.html

2.  Report of the seventh hacking sprint was put online:

    -   http://blog.darcs.net/2012/04/darcs-hacking-sprint-7-report.html

3.  BSRK Aditya was accepted as a Summer of Code student to work on the
    patch index optimization:

    -   http://www.google-melange.com/gsoc/project/google/gsoc2012/bsrkaditya/28002
    -   http://wiki.darcs.net/GSoC/2012-PatchIndex

# Issues resolved in the last week (4)

issue1166 Guillaume Hoffmann
  ~ -   --unified flag for record, amend-record, revert and unrevert
    -   http://bugs.darcs.net/issue1166

issue2065 Owen Stephens
  ~ -   filter and give warning for any malformed boring regexs.
    -   http://bugs.darcs.net/issue2065

issue2120 Adam Wolk
  ~ -   Darcs fails to invoke an editor under MS Windows
    -   http://bugs.darcs.net/issue2120

issue2139 Florent Becker
  ~ -   detect what to do when using darcs mv into/onto a directory
    -   http://bugs.darcs.net/issue2139


# Patches applied in the last week (111)

2012-04-24 Ganesh Sittampalam
  ~ -   update source link for 2.8 release

2012-04-05 Owen Stephens
  ~ -   Layout/Tidy of Patch.Bundle

2012-04-05 Ganesh Sittampalam
  ~ -   remove stale Tested-with entry from cabal file

2012-04-01 Owen Stephens
  ~ -   Haddock HashedRepo, and make a few fairly trivial refactorings
    -   Extract duplicated code in readInventoryPrivate, in HashedRepo
    -   Extract out the use of "pristine: " literal into an identifier
    -   Refactor listInventories function in HashedRepo
    -   Extract string literals for identifiers for inventories/pristine
    -   hlint suggestions to HashedRepo
    -   Change fmap -&amp;gt; &amp;lt;$&amp;gt; in HashedRepo
    -   Layout/tidy of Repository/HashedRepo
    -   Fix Patch.Set export list indentation

2012-04-06 Michael Hendricks
  ~ -   Implement exponential backoff test strategy
    -   Factor out function to build bisect strategy initial state
    -   Factor out initial test run
    -   Improve darcs test descriptive help
    -   Correct typos in trackdown-bisect test comments
    -   Consistent test strategy function naming
    -   Clearer test strategy selection
    -   Factor out Strategy type
    -   Unify darcs test strategy type signatures
    -   Use safeApply throughout Darcs.Commands.Test
    -   Style and Haddock for Darcs.Commands.Test

2012-04-17 Owen Stephens
  ~ -   Parse RepoFormat properties once, storing as an ADT, rather
than a ByteString.
    -   More tidying of Repository.Format
    -   Tidy Repository.Format
    -   Tidy Repository.Merge

2012-04-01 Ganesh Sittampalam
  ~ -   move URL.Curl to other-modules to avoid problems when curl
isn't available
    -   add a comment
    -   drop unnecessary superclasses from MyEq (PatchInfoAnd p)
    -   drop unnecessary call to joinPatches in Darcs.Resolution
    -   drop unnecessary call to joinPatches in Darcs.Repository.Merge

2012-03-31 Eric Kow
  ~ -   Replace CPP witness macros with plain Haskell in Darcs.SelectChanges.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.PrintPatch.hs
    -   Replace witness CPP macros with plain Haskell in
Darcs.Commands.AmendRecord

2012-04-01 Ganesh Sittampalam
  ~ -   fix name shadowing warning in Darcs.SelectChanges

2012-03-16 Guillaume Hoffmann
  ~ -   dirty fix for compile error in SelectChanges

2012-03-09 Andreas Brandt
  ~ -   Tidy up wspfr

2012-03-08 Guillaume Hoffmann
  ~ -   resolve issue1166 --unified flag for record, amend-record,
revert and unrevert
    -   change help of --unified to refer to changes in place of patches

2012-04-22 Florent Becker
  ~ -   Update current version in homepage

2012-04-20 Michael Hendricks
  ~ -   Patch 788 bundle

2012-04-01 Ganesh Sittampalam
  ~ -   import constructors of C types to deal with a GHC change
    -   fix deprecation about using unsafePerformIO from Foreign
    -   add missing type signatures
    -   remove unused imports in Darcs.Commands.Revert
    -   remove unused imports in Darcs.Ssh
    -   remove unused import in Darcs.Global
    -   remove unused import in Darcs.Patch.ApplyMonad
    -   fix name shadowing warnings in src/Darcs/Patch/ApplyMonad
    -   remove unused import in Darcs.Patch.Choices
    -   fix deprecated syntax in Darcs.Patch.Choices
    -   remove unusued imports in Darcs.Patch.Patchy.Instances
    -   remove redundant exports from Darcs.Patch.Prim
    -   remove unusued imports from Darcs.Patch.Prim.V1.Show
    -   remove unused import from Darcs.Patch.Prim.V1.Show
    -   add missing type signature in Darcs.Patch.Split
    -   switch from block/unblock to mask
    -   change from deprecated use of GHC.Handle.fdToHandle
    -   remove an no-longer-needed pragma
    -   remove unused import in Darcs.Patch.RepoPatch
    -   remove unused imports in Darcs.Patch.V1.Viewing
    -   remove unused imports in Darcs.Patch.V2.Non
    -   remove unused imports in Darcs.Patch.Viewing
    -   add missing type signatures in Darcs.Repository.HashedIO
    -   remove unused definition in Darcs.Repository.HashedIO
    -   remove unused import in Darcs.Repository.Prefs
    -   remove unused import in Darcs.Repository.Repair
    -   remove unused imports in Darcs.Repository.State
    -   remove unused variable in Darcs.Repository.State
    -   ignore name shadowing warnings in Darcs.Patch.V2.*
    -   fix some warnings in Darcs.Patch.Prim.V3.*
    -   silence various warnings for now
    -   silence warnings about Prelude.catch for now

2012-04-20 Michael Hendricks
  ~ -   Find latin9 locale on OS X too

2012-03-30 Simon Michael
  ~ -   be a little smarter about finding a latin9 locale for shell tests
    -   update utf8.sh test to suit the "last regrets" record prompt

2012-04-07 Ganesh Sittampalam
  ~ -   update for RC2

2012-04-20 Michael Hendricks
  ~ -   Patch 782 dependencies

2012-04-01 Eric Kow
  ~ -   Fix HTML typo in 2.8 RC announcement.

2012-04-01 Florent Becker
  ~ -   Announce 2.8 rc 1

2012-04-01 Ganesh Sittampalam
  ~ -   bump minimum GHC version
    -   fix build-tools constraint for test project

2012-04-20 Michael Hendricks
  ~ -   Patch 598 dependencies

2011-04-23 Owen Stephens
  ~ -   resolve issue2065: filter and give warning for any malformed
boring regexs.

2012-03-31 Eric Kow
  ~ -   Replace witness CPP macros with plain Haskell in Darcs.Match
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Diff

2012-03-15 Guillaume Hoffmann
  ~ -   remove two unused functions of Darcs.SelectChanges after darcs
diff optimization
    -   Optimize darcs diff

2012-03-31 Eric Kow
  ~ -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Move

2012-02-23 Adam Wolk
  ~ -   follow-up issue2120 : don't redirect stderr as it loses useful output
    -   resolve issue2120

2012-04-17 Owen Stephens
  ~ -   Add some Haddock to Patch.Commute
    -   Reorder some definitions in Patch.Commute
    -   Tidy Patch.Commute

2012-04-13 Michael Hendricks
  ~ -   Patch 775 dependencies

2012-03-31 Eric Kow
  ~ -   Remove now unused gadts.h

2012-04-13 Michael Hendricks
  ~ -   Patch 733 dependencies

2012-03-11 Owen Stephens
  ~ -   Fix some compile warnings in Commands/Move

2012-02-28 Florent Becker
  ~ -   Clean up Commands/Move.hs

2012-02-14 Ganesh Sittampalam
  ~ -   fix issue2139 test so it passes on darcs 2.5

2012-03-15 Michael Hendricks
  ~ -   Style and error message clean up for patch733

2012-02-28 Florent Becker
  ~ -   resolve issue2139: detect what to do when using darcs mv
into/onto a directory

2012-02-14 Ganesh Sittampalam
  ~ -   accept issue2139: problem with darcs mv path checking

2012-03-31 Eric Kow
  ~ -   Remove GADT_WITNESSES ifdef.
    -   Build Darcs once rather than thrice.

2012-04-01 Dave Love
  ~ -   Minor grammar fixes

2012-04-05 Owen Stephens
  ~ -   Fix name shadowing warning in Patch.Set
    -   Use haddock links in Patch.Set
    -   Use more informative identifier names in Patch.Set
    -   Tidy/style Patch.Set
&lt;/pre&gt;</description>
    <dc:creator>Guillaume Hoffmann</dc:creator>
    <dc:date>2012-04-27T19:48:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26377">
    <title>darcs 2.8 release</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26377</link>
    <description>&lt;pre&gt;Hi all,

The darcs team is pleased to announce the release of darcs 2.8.

Downloading
-----------

The easiest way to install darcs 2.8 from source is by first
installing the Haskell Platform (http://www.haskell.org/platform). If
you have installed the Haskell Platform or cabal-install, you can
install this release by doing:

$ cabal update
$ cabal install darcs-2.8

Alternatively, you can download the tarball from
http://darcs.net/releases/darcs-2.8.0.tar.gz and build it by hand as
explained in the README file.

The 2.8 branch is also available as a darcs repository from
http://darcs.net/releases/branch-2.8

Supported GHC versions and Unicode filenames.
---------------------------------------------

Due to changes in ghc's handling of non-ASCII filenames, darcs 2.8
supports GHC versions 6.10.x, 6.12.x, 7.0.x, and 7.4.x. Version 7.2.x is
also supported on Windows. On Unix systems, version 7.2.x is disabled by
the cabal file, as using a darcs executable built using ghc 7.2.x could
make the on-disk format of repositories inconsistent.

Binaries
--------

These will be posted to http://wiki.darcs.net/Binaries as they become
available.

Feedback
--------

If you have an issue with darcs 2.8, you can report it via the web
on http://bugs.darcs.net/ . You can also report bugs by email to bugs at
darcs.net, or come to #darcs on irc.freenode.net.

Most visible changes since darcs 2.5
------------------------------------

Since darcs 2.5 has been tagged, there have been 1181 patches accepted.
Here is a list of the most user-visible changes:

    -   Local support for the legacy "old-fashioned" repository format
        has been removed.
          ~ -   You can still work with remote repositories in this
                format
            -   Local repositories can still be upgraded via "darcs
                optimize --upgrade".
    -   "darcs annotate" is now significantly faster and uses less
        memory, although it still slows down linearly with repository
        size.
    -   An experimental option is available to speed up HTTP
        downloads.
          ~ -   You can now use "darcs optimize --http" to create a
                repo optimized for HTTP downloads, and use "darcs get
                --packs" to download such a repo.
            -   There are still some known issues with it, so the
                feature is not enabled by default.

    -   Darcs now supports multiple email addresses for the author in
        the global prefs file. So, if you use different identities for
        home and work, you can now easily select between them.
        (issue1530)
    -   The -o/-O options for obliterate which were removed in 2.5 are
        back.
    -   "darcs status" has been added as a hidden alias for "darcs
        whatnew -ls" to ease the transition from some other source
        control systems. (issue182)
    -   "darcs amend-record" now has the option --unrecord to allow
        individual changes to be unrecorded. (issue1470). This can
also be used as "darcs amend-unrecord".
    -   "darcs amend-record"'s interactive selection now supports 'k'
        for going back to a previous patch.
    -   "darcs dist" now has the option --set-scripts-executable.
        (issue734)
    -   pushing to ssh:// URLS is now supported. eg: darcs push
        ssh://code.haskell.org/foo
    -   If a test fails during darcs record, you now have the option
        to record it anyway. (issue332)
    -   Hunk-splitting now works in "darcs revert" (issue114)
    -   Sending patches by email is now more robust and human
        friendly. We display a cleaner version in plain text for
        humans, and have added a complete version of the patch for
        "darcs apply". (issue1350)
    -   "darcs send" now tries to report the right character set in
        the email headers, and has the option --charset to override
        this.
    -   A new environment variable has been added to help control
        network connections: DARCS\_CONNECTION\_TIMEOUT. See the
        manual for details.
    -   The --ephemeral and --partials options to "darcs get" has en
        removed. "darcs check --partial" has also been removed.
    -   "darcs rollback" now has a --no-record option, to be used en
        you only want to update the working directory.
    -   The --nolinks option for "darcs get" was removed.
    -   The "--old" flag has been removed for "darcs init", "darcs
        get" and "darcs put".
    -   "darcs resolve" has been removed an alias for "darcs
        mark-conflicts".
    -   "darcs init" and "darcs get" now have a --no-working-dir
        option.
    -   Conflicts are now marked with red in the terminal. ssue1681)
    -   ssh ControlMaster support has been removed.
    -   ssh stderr output is now passed through, making it easier to
        diagnose problems. (issue845)
    -   Interactive selection now has a 'g' command to go to the first
        patch.
    -   The --unified flag is now available for record, end-record,
        revert and unrevert (issue1166)
    -   darcs now has a "darcs test" command for running whatever
        test-suite is associated with the repository.

-   Other Issues resolved in Darcs 2.8
    -   issue1266: "darcs init" now warns when run inside another
        darcs repo.
    -   issue1344: When using darcs send, let users know sooner if
        they won't eventually be able to send
    -   issue1397: darcs changes /bad /paths no longer lists all
        changes
    -   issue1473: problem with annotate --repodir
    -   issue1551: Now we only use 'file content did not change'
        prompt for darcs send
    -   issue1558: xml output for patch hash no longer includes "gz"
        extension
    -   issue1599: automatically expire unused caches
    -   issue1637: When darcs get fails due to a HTTP failure, port
        the actual HTTP failure.
    -   issue1640: darcs apply --verbose docs have been improved
    -   issue1661: darcs add --quiet is quieter
    -   issue1705: fix error with unhandled --index in "darcs show
        contents"
    -   issue1714: provide more sensible behavior when combining an
        "ALL" default with a default for a specific sub-command
    -   issue1727: a better diagnostic message is provided when the
        user tries to move the root of the repository
    -   issue1740: "darcs mv" now gracefully the handles the case re
        the user first does an "mv" on a directory and then follows
        up with a "darcs mv"
    -   issue1804: The diagnostic message "getSymbolicLinkStatus: es
        not exist" has been improved
    -   issue1883: rename --patch-name option to --name. This is
        usually used in darcs record in shorthand (-m) form. This
        rename is aimed at eliminating the confusion with the patch
        matcher, which bites amend-record and rollback users.
    -   issue1884: darcs get was wrongly reporting "getting lazy
        repository" when you hit C-c
    -   issue1908: try to create a global cache before checking its
        availability
    -   issue1922: Fixed bug where obliterate -o was producing
        incorrect bundles in some cases
    -   issue1923: bad source warning mechanism no longer warns out
        sources outside your control
    -   issue1932: Handling of files with colons is improved
    -   issue1965: attempting "darcs move" on non-repo files now ves
        a sensible error
    -   issue1977: "darcs repair" now no longer complains if the
        pristine.hashed directory is missing
    -   issue1978: Improve handling of the \_darcs/format file with
        "darcs get"
    -   issue1984: "darcs convert" now gives a better error message
        for invalid repo names
    -   issue2013: "darcs send" no longer ignores --to (or default
        recipient) with --context
    -   issue2021: character encoding handling has been improved
    -   issue2041: "darcs add" no longer follows directory symlinks
    -   issue2054: The behavior when combining --boring with a ring
        file has been improved
    -   issue2066: "darcs record" better handles adding deleted and
        added files passed on the command line
    -   issue2067: darcs diff no longer outputs blank lines when
        non-existent files are given
    -   issue2076: "darcs move myfile" into directory confuses darcs
    -   issue2077: "darcs mv myfile" into directory no longer confuses
        darcs
    -   issue2079: "darcs put" now does --set-default by default


_______________________________________________
darcs-users mailing list
darcs-users&amp;lt; at &amp;gt;darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
&lt;/pre&gt;</description>
    <dc:creator>Florent Becker</dc:creator>
    <dc:date>2012-04-22T18:34:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26367">
    <title>darcs hacking sprint 7 report</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26367</link>
    <description>&lt;pre&gt;Hi all,

A bit over a week ago, we had the second half of the March Darcs hacking sprint, this time 6 of us in Southampton working on Darcs and Camp.

Here's a report of the two sprints
http://blog.darcs.net/2012/04/darcs-hacking-sprint-7-report.html

Thanks,

Eric

PS: next up… HCAR!

&lt;/pre&gt;</description>
    <dc:creator>Eric Kow</dc:creator>
    <dc:date>2012-04-09T12:18:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26365">
    <title>darcs 2.8 release candidate 2</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26365</link>
    <description>&lt;pre&gt;Hi all,

The darcs team is pleased to announce the release of darcs 2.7.99.2, aka
2.8 rc 2, the second release candidate for darcs 2.8.

Changes since 2.8 rc 1
----------------------
- Fixed compile errors on GHC 6.12, and corrected the unintentional
  omission of 6.12 from the release announcement.

- Fixed some warnings by pulling in any unconflicting patches to
  clean up warnings from mainline.

Downloading
-----------

The easiest way to install darcs 2.8 rc 2 from source is by first
installing the Haskell Platform (http://www.haskell.org/platform). If
you have installed the Haskell Platform or cabal-install, you can
install this release by doing:

$ cabal update
$ cabal install darcs-beta-2.7.99.2

Alternatively, you can download the tarball from
http://darcs.net/releases/darcs-2.7.99.2.tar.gz and build it by hand as
explained in the README file.

The 2.8 branch is also available as a darcs repository from
http://darcs.net/releases/branch-2.8

Supported GHC versions and Unicode filenames.
---------------------------------------------

Due to changes in ghc's handling of non-ASCII filenames, darcs 2.8rc1
supports GHC versions 6.10.x, 6.12.x, 7.0.x, and 7.4.x. Version 7.2.x is
also supported on Windows. On Unix systems, version 7.2.x is disabled by
the cabal file, as using a darcs executable built using ghc 7.2.x could
make the on-disk format of repositories inconsistent.

Binaries
--------

These will be posted to http://wiki.darcs.net/Binaries as they become
available.

Feedback
--------

If you have an issue with darcs 2.8 rc 2, you can report it via the web
on http://bugs.darcs.net/ . You can also report bugs by email to bugs at
darcs.net, or come to #darcs on irc.freenode.net.

Most visible changes since darcs 2.5
------------------------------------

Since darcs 2.5 has been tagged, there have been 1181 patches accepted.
Here is a list of the most user-visible changes:

    -   Local support for the legacy "old-fashioned" repository format
        has been removed.
          ~ -   You can still work with remote repositories in this
                format
            -   Local repositories can still be upgraded via "darcs
                optimize --upgrade".
    -   "darcs annotate" is now significantly faster and uses less
        memory, although it still slows down linearly with repository
        size.
    -   An experimental option is available to speed up HTTP
        downloads.
          ~ -   You can now use "darcs optimize --http" to create a
                repo optimized for HTTP downloads, and use "darcs get
                --packs" to download such a repo.
            -   There are still some known issues with it, so the
                feature is not enabled by default.

    -   Darcs now supports multiple email addresses for the author in
        the global prefs file. So, if you use different identities for
        home and work, you can now easily select between them.
        (issue1530)
    -   The -o/-O options for obliterate which were removed in 2.5 are
        back.
    -   "darcs status" has been added as a hidden alias for "darcs
        whatnew -ls" to ease the transition from some other source
        control systems. (issue182)
    -   "darcs amend-record" now has the option --unrecord to allow
        individual changes to be unrecorded. (issue1470). This can
also be used as "darcs amend-unrecord".
    -   "darcs amend-record"'s interactive selection now supports 'k'
        for going back to a previous patch.
    -   "darcs dist" now has the option --set-scripts-executable.
        (issue734)
    -   pushing to ssh:// URLS is now supported. eg: darcs push
        ssh://code.haskell.org/foo
    -   If a test fails during darcs record, you now have the option
        to record it anyway. (issue332)
    -   Hunk-splitting now works in "darcs revert" (issue114)
    -   Sending patches by email is now more robust and human
        friendly. We display a cleaner version in plain text for
        humans, and have added a complete version of the patch for
        "darcs apply". (issue1350)
    -   "darcs send" now tries to report the right character set in
        the email headers, and has the option --charset to override
        this.
    -   A new environment variable has been added to help control
        network connections: DARCS\_CONNECTION\_TIMEOUT. See the
        manual for details.
    -   The --ephemeral and --partials options to "darcs get" has en
        removed. "darcs check --partial" has also been removed.
    -   "darcs rollback" now has a --no-record option, to be used en
        you only want to update the working directory.
    -   The --nolinks option for "darcs get" was removed.
    -   The "--old" flag has been removed for "darcs init", "darcs
        get" and "darcs put".
    -   "darcs resolve" has been removed an alias for "darcs
        mark-conflicts".
    -   "darcs init" and "darcs get" now have a --no-working-dir
        option.
    -   Conflicts are now marked with red in the terminal. ssue1681)
    -   ssh ControlMaster support has been removed.
    -   ssh stderr output is now passed through, making it easier to
        diagnose problems. (issue845)
    -   Interactive selection now has a 'g' command to go to the first
        patch.
    -   The --unified flag is now available for record, end-record,
        revert and unrevert (issue1166)
    -   darcs now has a "darcs test" command for running whatever
        test-suite is associated with the repository.

-   Other Issues resolved in Darcs 2.8
    -   issue1266: "darcs init" now warns when run inside another
        darcs repo.
    -   issue1344: When using darcs send, let users know sooner if
        they won't eventually be able to send
    -   issue1397: darcs changes /bad /paths no longer lists all
        changes
    -   issue1473: problem with annotate --repodir
    -   issue1551: Now we only use 'file content did not change'
        prompt for darcs send
    -   issue1558: xml output for patch hash no longer includes "gz"
        extension
    -   issue1599: automatically expire unused caches
    -   issue1637: When darcs get fails due to a HTTP failure, port
        the actual HTTP failure.
    -   issue1640: darcs apply --verbose docs have been improved
    -   issue1661: darcs add --quiet is quieter
    -   issue1705: fix error with unhandled --index in "darcs show
        contents"
    -   issue1714: provide more sensible behavior when combining an
        "ALL" default with a default for a specific sub-command
    -   issue1727: a better diagnostic message is provided when the
        user tries to move the root of the repository
    -   issue1740: "darcs mv" now gracefully the handles the case re
        the user first does an "mv" on a directory and then follows
        up with a "darcs mv"
    -   issue1804: The diagnostic message "getSymbolicLinkStatus: es
        not exist" has been improved
    -   issue1883: rename --patch-name option to --name. This is
        usually used in darcs record in shorthand (-m) form. This
        rename is aimed at eliminating the confusion with the patch
        matcher, which bites amend-record and rollback users.
    -   issue1884: darcs get was wrongly reporting "getting lazy
        repository" when you hit C-c
    -   issue1908: try to create a global cache before checking its
        availability
    -   issue1922: Fixed bug where obliterate -o was producing
        incorrect bundles in some cases
    -   issue1923: bad source warning mechanism no longer warns out
        sources outside your control
    -   issue1932: Handling of files with colons is improved
    -   issue1965: attempting "darcs move" on non-repo files now ves
        a sensible error
    -   issue1977: "darcs repair" now no longer complains if the
        pristine.hashed directory is missing
    -   issue1978: Improve handling of the \_darcs/format file with
        "darcs get"
    -   issue1984: "darcs convert" now gives a better error message
        for invalid repo names
    -   issue2013: "darcs send" no longer ignores --to (or default
        recipient) with --context
    -   issue2021: character encoding handling has been improved
    -   issue2041: "darcs add" no longer follows directory symlinks
    -   issue2054: The behavior when combining --boring with a ring
        file has been improved
    -   issue2066: "darcs record" better handles adding deleted and
        added files passed on the command line
    -   issue2067: darcs diff no longer outputs blank lines when
        non-existent files are given
    -   issue2076: "darcs move myfile" into directory confuses darcs
    -   issue2077: "darcs mv myfile" into directory no longer confuses
        darcs
    -   issue2079: "darcs put" now does --set-default by default


_______________________________________________
darcs-users mailing list
darcs-users&amp;lt; at &amp;gt;darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
&lt;/pre&gt;</description>
    <dc:creator>Ganesh Sittampalam</dc:creator>
    <dc:date>2012-04-07T21:26:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26362">
    <title>Symbolic links in place of removed files</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26362</link>
    <description>&lt;pre&gt;Hi all,

I'm looking for some advice about the following darcs behaviour. I 
haven't found it reported in the issue tracker, but some issues seems 
similar enough so that I'm wondering if I should report it.

$ darcs initialize
$ touch foo bar
$ darcs record -lam first
Finished recording patch 'first'
$ rm foo ; ln -s bar foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am second
No changes!

Note that it would succeed (record the file removal) if I used either 
`darcs remove' or `darcs record -l'. Anyway this is only triggered by 
the presence of the symbolic link:

$ rm foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am second
Finished recording patch 'second'

What really hurts is the case in which the link addresses a not-existent 
file:

$ touch foo
$ darcs record -lam third
Finished recording patch 'third'
$ rm foo ; ln -s qux foo
$ darcs whatsnew -ls
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such file or directory)
$ darcs record -am fourth
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such file or directory)
$ darcs remove foo
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such file or directory)
$ darcs record -lam fourth
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such file or directory)

The last two command would have 'fixed' the repository had the link 
addressed an existent file. In this case however the only solution seems 
to be removing the link:

$ rm foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am fourth
Finished recording patch 'fourth'

Any thoughts ? Is it someway expected (read: dependant on some already 
reported issue) ?

Thanks,
Gian Piero.
&lt;/pre&gt;</description>
    <dc:creator>Gian Piero Carrubba</dc:creator>
    <dc:date>2012-04-05T22:11:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26357">
    <title>darcs weekly news #94</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26357</link>
    <description>&lt;pre&gt;# News and discussions

1.  The Southampton sprint is over! We'll put together a blog report soon.

2.  Florent and Ganesh prepared a release candidate of Darcs 2.8, try it!
    -   http://lists.osuosl.org/pipermail/darcs-users/2012-April/026445.html
    -   http://lists.osuosl.org/pipermail/darcs-users/2012-April/026448.html

3.  What would be the next big feature of Darcs 2.10? Ganesh proposed rebase,
    and Michael already provided feedback about this feature:
    -   http://lists.osuosl.org/pipermail/darcs-users/2012-April/026443.html
    -   http://lists.osuosl.org/pipermail/darcs-users/2012-April/026455.html

4.  Eric asked what would be a nice mission statement for Darcs.
    A few propositions have been made so far:
    -   http://lists.osuosl.org/pipermail/darcs-users/2012-March/026433.html


# Issues resolved in the last week (3)

issue2125 Owen Stephens
  ~ -   only warn about forcing replaces, when a force is required.
    -   http://bugs.darcs.net/issue2125

issue2136 Owen Stephens
  ~ -   Correctly track renames of multiple files in Changes --xml.
    -   http://bugs.darcs.net/issue2136

issue2162 Owen Stephens
  ~ -   Fix compilation failure with GHC 6.12
    -   http://bugs.darcs.net/issue2162


# Patches applied in the last week (199)

2012-04-03 Michael Hendricks
  ~ -   Haddock for Darcs.Patch.Info.patchinfo

2012-04-01 Eric Kow
  ~ -   Convert Printer.lhs from literate Haskell.

2012-04-02 Owen Stephens
  ~ -   Tidy and slightly refactor ProgressPatches
    -   Tweak command name in unrevert
    -   Remove some duplicate code and slight tidy in Repository.LowLevel
    -   Tidy/Style Repository.LowLevel
    -   Style/tidy Respository.Motd
    -   Remove warnings in Darcs.Test.Patch
    -   Remove warnings from Patch.Properties.Generic
    -   Disable all warnings for Arbitrary.PrimV3
    -   Fix warning in Arbitrary.Generic
    -   Remove warnings from Arbitrary.PatchV1
    -   Remove trailing whitespace from Darcs.Test.Patch.V1Model
    -   Remove compile warnings from Darcs.Test.Patch.V1Model
    -   Disable all warnings for Test.Patch.V3Model
    -   Remove warnings in Darcs.Test.Patch.RepoModel
    -   Use System.IO.Unsafe for unsafePerformIO, not Foreign
    -   Remove an unused import in Test.Patch.Properties.V1Set2
    -   Remove compile warnings in Test.Patch.Properties.Check
    -   Remove do-notation warning from Workaround
    -   Remove do-notation warning from Compat
    -   Remove do-notation warning from External
    -   Remove do-notation warning from Repository.HashedIO
    -   Remove do-notation warning from Repository.Merge
    -   Remove do-notation warning from Repository.Internal
    -   Remove do-notation warning from Commands.Get
    -   remove two do-notation warnings from Commands.Unrecord
    -   Remove two do-notation warnings from Commands.Optimize
    -   Remove do-notation warning in Commands.Tag
    -   Remove four do-notation warnings in Commands.Record
    -   Remove two do-notation warnings in SignalHandler
    -   Remove two do-notation warnings in Lock
    -   Remove do-notation warning in RunCommand
    -   Remove two do-notation warnings in Repository
    -   Remove a do-notation warning in URL.
    -   Tidy/style Repository.ApplyPatches

2012-03-31 Eric Kow
  ~ -   Remove unused "gadts.h" import from Progress
    -   Replace CPP witness macros with plain Haskell in
Darcs.Witnesses.Unsafe.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Witnesses.Show.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Witnesses.Sealed.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Witnesses.Ordered.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Witnesses.Eq.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Resolution.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.State.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Repair.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Prefs.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Repository.Old.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Merge.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.LowLevel.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.InternalTypes.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Internal.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.HashedRepo.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.HashedIO.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Format.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.Cache.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Repository.ApplyPatches.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Repository.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.ProgressPatches.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Viewing.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V2.Real.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V2.Non.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Patch.V1.Viewing.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V1.Show.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V1.Read.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V1.Core.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Patch.V1.Commute.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.V1.Apply.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Patch.TouchesFiles.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Summary.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Split.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Show.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Set.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Repair.hs
    -   Replace CPP witness macros with plain Haskell in Darcs.Patch.Read.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Patch.Prim.V3.Show.hs
    -   Replace CPP witness macros with plain Haskell in
Darcs.Patch.Prim.V3.Details.hs
    -   Replace witness CPP macros with plain Haskell in Darcs.Witnesss.WZipper
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V3.Core
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V3.Commute
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V3.Coalesce
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V3.Apply
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Show
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Read
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Details
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Core
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Commute
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Coalesce
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Prim.V1.Apply
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Prim.Class
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Permutations
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Patchy
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.PatchInfoAnd
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Named
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Merge
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Match
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Invert
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Inspect
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Format
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.FileHunk
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Effect
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Dummy
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Depends
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.ConflictMarking
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Conflict
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Commute
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Choices
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Bundle
    -   Replace witness CPP macros with plain Haskell in
Darcs.Patch.Bracketed.Instances
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Bracketed
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch.Apply
    -   Replace witness CPP macros with plain Haskell in Darcs.Patch
    -   Replace witness CPP macros with plain Haskell in Darcs.Diff
    -   Replace witness CPP macros with plain Haskell in Darcs.CommandsAux
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.WhatsNew
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Util
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Unrevert
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Unrecord
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Test
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Tag
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.ShowRepo
    -   Replace witness CPP macros with plain Haskell in
Darcs.Commands.ShowIndex
    -   Replace witness CPP macros with plain Haskell in
Darcs.Commands.ShowFiles
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Send
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Rollback
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Revert
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Replace
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Repair
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Remove
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Record
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Put
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Push
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Pull
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Optimize
    -   Replace witness CPP macros with plain Haskell in
Darcs.Commands.MarkConflicts
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Get
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.GZCRCs
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Convert
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Changes
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Apply
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Annotate
    -   Replace witness CPP macros with plain Haskell in Darcs.Commands.Add
    -   Replace witness CPP macros with plain Haskell in Darcs.Arguments
    -   Replace witness CPP macros with plain Haskell in Darcs.Annotate
    -   Replace witness CPP macros with plain Haskell in test_stub
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.WithState
    -   Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.WSub
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.V3Model
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.V1Model
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.V1Set2
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.V1Set1
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.Real
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.GenericUnwitnessed
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.Generic
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Properties.Check
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Examples.Set2Unwitnessed
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Examples.Set1
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Arbitrary.Real
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Arbitrary.PrimV3
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Arbitrary.PrimV1
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Arbitrary.PatchV1
    -   Replace witness CPP macros with plain Haskell in
Darcs.Test.Patch.Arbitrary.Generic
    -   Replace witness CPP macros with plain Haskell in Darcs.Test.Patch
    -   Replace witness CPP macros with plain Haskell in Darcs.Test.Misc

2012-03-31 Simon Michael
  ~ -   another fix for utf8.sh test, update to current rollback ui

2012-03-27 Michael Hendricks
  ~ -   List conflicted files one per line

2012-03-24 Guillaume Hoffmann
  ~ -   make darcs test more consistent
    -   update manual for darcs test and repair --dry-run
    -   make check an alias for repair --dry-run
    -   add regression test to check warning message presence for darcs test
    -   switch to test --trackdown and test --bisect
    -   adapt testsuite to test --trackdown and test --bisect
    -   adapt test suite to switch from darcs check to darcs test
    -   introduce darcs test, doing the same as did check --test
without repo check
    -   Remove the function delimiters

2012-02-14 Will Langstroth
  ~ -   Organize export list in Darcs.Patch
    -   Haddock-friendly formatting for Darcs.Patch.Apply

2012-01-31 Owen Stephens
  ~ -   Fix improper handling of FileNames that are prefixes-of, but
not parents-of a target FileName.
    -   Add current_name attribute to created_as in changes --xml on
multiple files.
    -   Resolve Issue2136: Correctly track renames of multiple files
in Changes --xml.
    -   Rename withFilePaths -&amp;gt; withFileNames, since it operates on
FileNames not FilePaths.
    -   Replace applyToFilepaths with applyToFilePaths to match casing
of FilePath
    -   Add new helper function to determine if a given filename is
the parentOrEqual of another.
    -   Use &amp;lt;$&amp;gt; instead of fmap in Patch/Apply.hs
    -   Refactor movedirfilename to use stripPrefix lib function,
rather than equivalent hand-rolled code.

2012-03-29 Andreas Brandt
  ~ -   Added comments for withDir and some style improvements

2012-03-26 Guillaume Hoffmann
  ~ -   style and cleanup Darcs.Repository.Internal

2012-02-24 Dave Love
  ~ -   Reinstate newlines lost in fix for issue1681

2012-03-26 Guillaume Hoffmann
  ~ -   style and cleanup Darcs.Commands.Get and Darcs.Repository

2012-03-30 Owen Stephens
  ~ -   Add check for token in working copy to issue2125 test. Remove
obsolete test for issue864.
    -   Follow up to resolve issue2125, with style changes
    -   Resolve issue2125: only warn about forcing replaces, when a
force is required.
    -   Accept issue 2125: darcs replace always warns about forcing,
even when unnecessary
    -   Refactor/tidy-up Commands/Replace
    -   Extract common token-breaking code in Patch/TokenReplace
    -   Tidy Patch/TokenReplace
    -   camelcase a few identifiers in Commands/Replace
    -   Tidy Commands/Replace
    -   Resolve issue2162
    -   Style, tidy and start commenting Real.hs
&lt;/pre&gt;</description>
    <dc:creator>Guillaume Hoffmann</dc:creator>
    <dc:date>2012-04-04T17:37:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26339">
    <title>rebase feedback and amend-record flexibility</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26339</link>
    <description>&lt;pre&gt;I've been playing with the rebase branch for the last couple weeks.  Here's
a lengthy brain dump.  If you're interested in more explanation for any
particular point, let me know.

   - suspend and unsuspend
      - have proven very useful
      - would be good building blocks for branch, rebase and stash plugins
      - should be top-level commands like record/unrecord, pull/unpull,
      revert/unrevert
      - are too low level to satisfactorily solve the deep amend problem
      for users
      - need a way to list suspended patches (darcs changes --suspended?)
   - pull
      - should be "darcs pull --suspend-conflicts"
      - even better would be "darcs pull
      --conflicts={mark,allow,disallow,skip,suspend-ours,suspend-theirs}"
      - suspending conflicted patches might offer more pleasant conflict
      resolution, one offender at a time
   - obliterate
      - should be "darcs obliterate --suspended"?
   - reify, inject
      - I don't understand the purpose of these commands
      - should their function be hidden in the implementation of
      suspend/unsuspend?
   - rebase command is superfluous UI
      - as mentioned above, most subcommands belong elsewhere
      - Darcs already has UI for accomplishing the same goals as
      Git/Mercurial rebase, no new UI needed except perhaps interactive rebase
      for performing bulk history-edit operations

Users coming from Git or Mercurial are likely to think of rebase in the
following use cases:

   - moving patches from one branch to another (the original Git use case)
      - "darcs push --obliterate" could remove the pushed patches from the
      local repo on success
   - commuting patches to better convey intent
      - perhaps makes less sense in darcs
      - sometimes useful to bring a few patches to the front so they're
      quicker to access during interactive patch selection
      - "git rebase --interactive" UI is the best I've seen for bulk
      commute operations
      - maybe best done as an interactive rebase plugin
   - rewording commit messages, changing author, changing date, etc
      - amend-record does this, it's just not smart enough yet
      - rewording a patch needs no commute operations
      - dependencies should never prevent a reword operation
      - rewording a buried darcs patch only modifies other patches if there
      are "record --ask-deps" dependencies (which appear easy to adjust
      automatically)
   - changing the effect of earlier patches
      - amend-record does this but isn't smart enough yet
      - is really "commute two patches to be adjacent then coalesce them"
      - commuting patches to be adjacent is more likely to succeed than
      commuting a buried patch to the front
      - amend-record can't do this yet because it selects patches before it
      selects changes
   - combining arbitrary, adjacent patches
      - Darcs internals call this coalesce, but we have no UI for it
      - current amend-record is a special case of this, applied to only the
      top two patches
      - maybe a new darcs command (combine,coalesce,squash)?
   - splitting a single patch into multiple, adjacent patches
      - conceptually similar to combining patches
      - maybe a new darcs command (split, uncombine, uncoalesce)?

In most of the above use cases, suspend/unsuspend is only needed as a last
attempt when normal commute/coalesce operations fail.  With some
adjustments, such failures should be relatively rare.

Thus ends my lengthy brain dump

&lt;/pre&gt;</description>
    <dc:creator>Michael Hendricks</dc:creator>
    <dc:date>2012-04-02T16:09:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26336">
    <title>Google Summer of Code (6 April)</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26336</link>
    <description>&lt;pre&gt;Hi all,

Just a quick reminder that the Google Summer of Code is upon us.

The deadline is coming up pretty quickly (Fri 6 April), so best get in touch if you want feedback on your proposals!

http://www.google-melange.com/gsoc/events/google/gsoc2012

Thanks,

&lt;/pre&gt;</description>
    <dc:creator>Eric Kow</dc:creator>
    <dc:date>2012-04-01T16:09:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26329">
    <title>darcs 2.8 release candidate 1</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26329</link>
    <description>&lt;pre&gt;Hi all,

The darcs team is pleased to announce the release of darcs 2.7.99.1, aka
2.8 rc 1, the first release candidate for darcs 2.8.

Downloading
-----------

The easiest way to install darcs 2.8 rc 1 from source is by first
installing the Haskell Platform (http://www.haskell.org/platform). If
you have installed the Haskell Platform or cabal-install, you can
install this release by doing:

$ cabal update
$ cabal install darcs-2.7.99.1

Alternatively, you can download the tarball from
http://darcs.net/releases/darcs-2.7.99.1.tar.gz and build it by hand as
explained in the README file.

The 2.8 branch is also available as a darcs repository from
http://darcs.net/releases/branch-2.8

Supported GHC versions and Unicode filenames.
---------------------------------------------

Due to changes in ghc's handling of non-ASCII filenames, darcs 2.8rc1
supports GHC versions 6.10.x, 7.0.x, and 7.4.x. Version 7.2.x is also
supported on Windows. On Unix systems, version 7.2.x is disabled by the
cabal file, as using a darcs executable built using ghc 7.2.x could make
the on-disk format of repositories inconsistent.

Binaries
--------

These will be posted to http://wiki.darcs.net/Binaries as they become
available.

Feedback
--------

If you have an issue with darcs 2.8 rc 1, you can report it via the web
on http://bugs.darcs.net/ . You can also report bugs by email to bugs at
darcs.net, or come to #darcs on irc.freenode.net.

Most visible changes since darcs 2.5
------------------------------------

Since darcs 2.5 has been tagged, there have been 1138 patches accepted.
Here is a list of the most user-visible changes:

    -   Local support for the legacy "old-fashioned" repository format
        has been removed.
          ~ -   You can still work with remote repositories in this
                format
            -   Local repositories can still be upgraded via "darcs
                optimize --upgrade".
    -   "darcs annotate" is now significantly faster and uses less
        memory, although it still slows down linearly with repository
        size.
    -   An experimental option is available to speed up HTTP
        downloads.
          ~ -   You can now use "darcs optimize --http" to create a
                repo optimized for HTTP downloads, and use "darcs get
                --packs" to download such a repo.
            -   There are still some known issues with it, so the
                feature is not enabled by default.

    -   Darcs now supports multiple email addresses for the author in
        the global prefs file. So, if you use different identities for
        home and work, you can now easily select between them.
        (issue1530)
    -   The -o/-O options for obliterate which were removed in 2.5 are
        back.
    -   "darcs status" has been added as a hidden alias for "darcs
        whatnew -ls" to ease the transition from some other source
        control systems. (issue182)
    -   "darcs amend-record" now has the option --unrecord to allow
        individual changes to be unrecorded. (issue1470). This can
also be used as "darcs amend-unrecord".
    -   "darcs amend-record"'s interactive selection now supports 'k'
        for going back to a previous patch.
    -   "darcs dist" now has the option --set-scripts-executable.
        (issue734)
    -   pushing to ssh:// URLS is now supported. eg: darcs push
        ssh://code.haskell.org/foo
    -   If a test fails during darcs record, you now have the option
        to record it anyway. (issue332)
    -   Hunk-splitting now works in "darcs revert" (issue114)
    -   Sending patches by email is now more robust and human
        friendly. We display a cleaner version in plain text for
        humans, and have added a complete version of the patch for
        "darcs apply". (issue1350)
    -   "darcs send" now tries to report the right character set in
        the email headers, and has the option --charset to override
        this.
    -   A new environment variable has been added to help control
        network connections: DARCS\_CONNECTION\_TIMEOUT. See the
        manual for details.
    -   The --ephemeral and --partials options to "darcs get" has en
        removed. "darcs check --partial" has also been removed.
    -   "darcs rollback" now has a --no-record option, to be used en
        you only want to update the working directory.
    -   The --nolinks option for "darcs get" was removed.
    -   The "--old" flag has been removed for "darcs init", "darcs
        get" and "darcs put".
    -   "darcs resolve" has been removed an alias for "darcs
        mark-conflicts".
    -   "darcs init" and "darcs get" now have a --no-working-dir
        option.
    -   Conflicts are now marked with red in the terminal. ssue1681)
    -   ssh ControlMaster support has been removed.
    -   ssh stderr output is now passed through, making it easier to
        diagnose problems. (issue845)
    -   Interactive selection now has a 'g' command to go to the first
        patch.
    -   The --unified flag is now available for record, end-record,
        revert and unrevert (issue1166)
    -   darcs now has a "darcs test" command for running whatever
        test-suite is associated with the repository.

-   Other Issues resolved in Darcs 2.8
    -   issue1266: "darcs init" now warns when run inside another
        darcs repo.
    -   issue1344: When using darcs send, let users know sooner if
        they won't eventually be able to send
    -   issue1397: darcs changes /bad /paths no longer lists all
        changes
    -   issue1473: problem with annotate --repodir
    -   issue1551: Now we only use 'file content did not change'
        prompt for darcs send
    -   issue1558: xml output for patch hash no longer includes "gz"
        extension
    -   issue1599: automatically expire unused caches
    -   issue1637: When darcs get fails due to a HTTP failure, port
        the actual HTTP failure.
    -   issue1640: darcs apply --verbose docs have been improved
    -   issue1661: darcs add --quiet is quieter
    -   issue1705: fix error with unhandled --index in "darcs show
        contents"
    -   issue1714: provide more sensible behavior when combining an
        "ALL" default with a default for a specific sub-command
    -   issue1727: a better diagnostic message is provided when the
        user tries to move the root of the repository
    -   issue1740: "darcs mv" now gracefully the handles the case re
        the user first does an "mv" on a directory and then follows
        up with a "darcs mv"
    -   issue1804: The diagnostic message "getSymbolicLinkStatus: es
        not exist" has been improved
    -   issue1883: rename --patch-name option to --name. This is
        usually used in darcs record in shorthand (-m) form. This
        rename is aimed at eliminating the confusion with the patch
        matcher, which bites amend-record and rollback users.
    -   issue1884: darcs get was wrongly reporting "getting lazy
        repository" when you hit C-c
    -   issue1908: try to create a global cache before checking its
        availability
    -   issue1922: Fixed bug where obliterate -o was producing
        incorrect bundles in some cases
    -   issue1923: bad source warning mechanism no longer warns out
        sources outside your control
    -   issue1932: Handling of files with colons is improved
    -   issue1965: attempting "darcs move" on non-repo files now ves
        a sensible error
    -   issue1977: "darcs repair" now no longer complains if the
        pristine.hashed directory is missing
    -   issue1978: Improve handling of the \_darcs/format file with
        "darcs get"
    -   issue1984: "darcs convert" now gives a better error message
        for invalid repo names
    -   issue2013: "darcs send" no longer ignores --to (or default
        recipient) with --context
    -   issue2021: character encoding handling has been improved
    -   issue2041: "darcs add" no longer follows directory symlinks
    -   issue2054: The behavior when combining --boring with a ring
        file has been improved
    -   issue2066: "darcs record" better handles adding deleted and
        added files passed on the command line
    -   issue2067: darcs diff no longer outputs blank lines when
        non-existent files are given
    -   issue2076: "darcs move myfile" into directory confuses darcs
    -   issue2077: "darcs mv myfile" into directory no longer confuses
        darcs
    -   issue2079: "darcs put" now does --set-default by default
&lt;/pre&gt;</description>
    <dc:creator>Florent Becker</dc:creator>
    <dc:date>2012-04-01T09:46:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26327">
    <title>rebase in mainline?</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26327</link>
    <description>&lt;pre&gt;Hi,

I'm thinking about merging rebase into HEAD, for release in 2.10
(there'll be lots of conflicts so I would actually rebase the code).

There would still need to be significant work on it and its UI, and if
we don't manage to get it ready in time we could ship 2.10 with it
disabled-by-default. However I think it is time to open it up for wider
testing and feedback, and create some pressure to actually get it out.

Any thoughts/objections?

Cheers,

Ganesh
&lt;/pre&gt;</description>
    <dc:creator>Ganesh Sittampalam</dc:creator>
    <dc:date>2012-04-01T08:35:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26326">
    <title>darcs wiki now using Markdown</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26326</link>
    <description>&lt;pre&gt;Hi all,

Just a heads-up for anybody who edits the wiki: We've switched from reStructuredText to Markdown (using Pandoc for our auto-conversion).

http://wiki.darcs.net

Hopefully any breakage this has caused will be easy to fix.

This switch is entirely motivated by network effects.  These days, Markdown usage is so widespread (off the top of my head, GitHub, Reddit, StackOverflow...), and enough people are familiar with it that it'd be a bit silly to ask people to have to learn two lightweight text formats just to make a little change to the wiki.

Thanks much to Trent, Mark and others who have pushed for our usage of reStructuredText.  If recall correctly,

1. When Trent was serving as doc manager, he advocated a separation of the user manual from the code (done now, thanks to Guillaume), and a switch from TeX to RST

2. When we switched from MoinMoin to Gitit, I decided to go with RST to avoid having two text formats within the community.

3. Now I'm going to assume that the arguments made 4 years ago in favour of RST (extensibility, convertibility with nice tools, good pdf/etc output) are now overwhelmed by the sheer popularity of Markdown and the fact that we're using Pandoc anyway.

Thanks.  And apologies if I've stepped on any toes in the process!  Erring more on the side of just doing things.

Eric

[1] http://lists.osuosl.org/pipermail/darcs-users/2008-October/014883.html

&lt;/pre&gt;</description>
    <dc:creator>Eric Kow</dc:creator>
    <dc:date>2012-03-31T17:16:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.version-control.darcs.user/26320">
    <title>correcting typos with amend-record</title>
    <link>http://comments.gmane.org/gmane.comp.version-control.darcs.user/26320</link>
    <description>&lt;pre&gt;Imagine that I have patches A and B.  B depends on A.  I discover that A's
patch name and long comment have a major typo.  Unfortunately, "darcs
amend-record --edit-long-comment -p A" won't work.  B's dependency prevents
A from being commuted to the front even though changing A's metadata won't
affect B at all.

I want an option letting me change A's metadata regardless of the
dependencies.  Would such an option be useful to others?  What should it be
called?

  darcs amend-record --none --edit-long-comment
  darcs amend-record --metadata-only --edit-long-comment

I'm partial to --none since it's the opposite of --all.

Ideally, amend-record would prompt for changes before prompting for which
patch to amend.  That way, if the user selects no changes Darcs can skip
dependency analysis when presenting patches.  Would changing the prompt
order harm your favorite use cases?

&lt;/pre&gt;</description>
    <dc:creator>Michael Hendricks</dc:creator>
    <dc:date>2012-03-30T22:34:39</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.version-control.darcs.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.version-control.darcs.user</link>
  </textinput>
</rdf:RDF>

