Hi Alexander,
Darcs currently does not support signing data inside of repositories.
It does only provide *patch bundle* signing in the "darcs send"
command and checking the signature in "darcs apply".
Now, patch signing in Darcs seems dificult to implement because
context changes modify the
HI all,
Although it is uncertain at which rate Darcs' development is going to
happen in the next months, I'd like to make a little summary of what
we could do now:
* since we now require GHC >= 7.10 we can grep through the TODO's in
the source code and try to fix those that wish for new GHC
be installed via cabal or (soon) stack. The 2.12
branch is also available as a darcs repository from
http://darcs.net/releases/branch-2.12 .
Thanks!
Guillaume Hoffmann
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman
Ah :)
Yes, what you described would be an "ideal" patch for that case.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
In the example you gave, "darcs record" just removes the "a" line
(current or old diff algorithm).
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Hi Henning,
You are right saying that Darcs matches exactly equal lines.
I'm afraid that what you are proposing is not possible with Darcs'
current internal representation of patches. Darcs handles patches in a
line-based way. So the problem is worse than computationnal cost.
But a future and
patch viewing via the
"darcs annotate" command. (Guillaume Hoffmann)
* `whatsnew -s` (and `status`) show conflicting files (Guillaume Hoffmann)
* honor "quiet" flag in command outputs (Ben Franksen)
* a single `show patch-index` command (Guillaume Hoffmann)
* remove deprec
Hi,
the 2.12 branch is available at http://darcs.net/releases/branch-2.12
Supported GHC versions are from 7.6 to the latest 8 rc3 (thanks to
patches by Ganesh). Testers are welcome!
The current target release day is thursday 28/4.
Guillaume
___
- <http://lists.osuosl.org/pipermail/darcs-users/2016-April/027197.html>
- <http://darcs.net/Sprints/2016-05>
# Issues resolved (5)
issue1807 Guillaume Hoffmann
~ - clarify help of PAGER, DARCS_PAGER
- <http://bugs.darcs.net/issue1807>
issue2258 Guillaume Hoffma
In the light of the next Darcs/Pijul sprint, and in the light of the
lack of GHC 8 (yet), I would like to release Darcs 2.12 by the end of
this month.
My current plan is:
* Thursday 21st of April : clone branch-2.12 from reviewed
* Some day until (and including) Friday 29th of April: unleash
# News and discussions
1. After 7 years of being the maintainer/Benevolent Dictator of Darcs,
Eric Kow stepped down and offered me (Guillaume Hoffmann) to take over,
which I accepted:
- <http://lists.osuosl.org/pipermail/darcs-users/2015-October/027144.html>
-
Thanks for testing with GHC8!
OK for stash; I agree to favour a sound release date over having a
particular feature included in 2.12.
Guillaume
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Hi everyone,
we had an important release of Darcs 2.10.0 on April of 2015, and the
last point-release is 2.10.3 from January of 2016.
I'm aiming at releasing Darcs 2.12 whithin the next couple of months
to avoid waiting too long for another "big release" which would cost
us too much effort.
I
The darcs team is pleased to announce the release of darcs 2.10.3 !
# Downloading #
One way of installing Darcs 2.10.3 is with stack:
$ stack install darcs-2.10.3
Or first install the Haskell Platform (http://www.haskell.org/platform)
and install Darcs with cabal-install:
$ cabal update
$
> I assumed that 'darcs test' is the replacement 'darcs check --test', isn't
> it? 'darcs test --help' says that '--once' is the default. Ok, but I was not
> aware, that 'darcs test' also replaces 'trackdown'.
You're right and I was wrong!
"darcs test" is indeed the replacement of "darcs check
Hi Henning,
> Older darcs versions (e.g. darcs-2.5) had the 'trackdown' function.
> http://darcs.net/manual/Darcs_commands.html#SECTION006112000
>
> It seems to be removed in darcs-2.10. I wonder how it can work if many
> interim states do not compile.
It is present in 2.10 under
Dear hackers,
happy new year to everyone!
This is a reminder for the people interested in participating. Please
contact us ASAP so that we can grant you access to the university
during the weekend.
See http://wiki.darcs.net/Sprints/2016-01 .
Thanks
Guillaume
2015-12-15 17:18 GMT-03:00 Ganesh Sittampalam :
> I think showing the XORed hashes is a good idea. We've previously held
> back because of not being able to do the reverse mapping easily, but
> something is better than nothing.
I looked but haven't found previous discussion about
More info about the different hashes that Darcs uses:
http://darcs.net/Internals/Hashes
The XOR I propose is on hash #1.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Hi everyone,
As said by David Leuschner in a previous mail, one of the shortcomings
of Darcs is:
"it's not as easy to refer to a specific state of the repository using a hash".
As a developer I know that Darcs uses (internally) the pristine hash,
which is a hash of the recorded working copy.
Dear Hackers
I'm glad to announce that the 10th Darcs Sprint that will be in
Seville, on January 15-17 at the ETS de Ingeniería Informática,
Universidad de Sevilla.
Please check the details at:
http://darcs.net/Sprints/2016-01
Here are three things to know
1. Everybody is welcome to join us.
The darcs team is pleased to announce the release of darcs 2.10.2 !
# Downloading #
The easiest way to install darcs 2.10.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
Hi David,
> At the moment I don't really know what to expect from Darcs. The Darcs
> development team is passionate and highly competent but very small. I also
> don't know what the direction will be. What are the major improvements
> you'd all like to work on?
Right now, I'm not working on
An update, here are the patches that are currently accepted for darcs
2.10.2 are:
* remove redundant import
* drop sandi lower bound to support GHC 7.4 and add an upper bound
* Switch from dataenc (deprecated) to sandi
* replace changes by log in two help strings
* make patch selection
Hi everyone,
I guess I should say a few words about this :-)
First I'd like to thank Eric for his work as a maintainer for 7 years,
and hope he'll stick around!
For the observers that might wonder what is going to change for the
Darcs project, the answer is: not much.
Ever since I started
Just a reminder that the next Darcs sprint is *this weekend* from
Friday to Sunday in Paris.
Have a look below for more details!
2015-08-21 15:58 GMT-03:00 Guillaume Hoffmann <guilla...@gmail.com>:
> Dear Hackers
>
> the next Darcs Sprint that will be in Paris, on September 1
Hi,
I'd like to know if people needed a darcs 2.10.2 release soon, and if
there are changes/bugs that we should particularly look at?
Since we're doing the Hacking Sprint this weekend, we can have a look
at the issues you think are most urgent.
Don't hesitate to nag me by answering this mail
Darcs 2.10.1 has been released (bugfixes, dependency versions bump):
- <http://lists.osuosl.org/pipermail/darcs-users/2015-July/027130.html>
# Issues resolved (19)
issue2102 Guillaume Hoffmann
~ - document packs in help of clone and optimize http
- <http://bugs.darcs.net/
Dear Hackers
the next Darcs Sprint that will be in Paris, on September 18-20 at
IRILL (near Place d'Italie).
Please check out the details at:
http://darcs.net/Sprints/2015-09
Here are three things to know
1. Everybody is welcome to join us. We'd love to have you, whatever
your Haskell or
Hi all,
The darcs team is pleased to announce the release of darcs 2.10.1 !
# Downloading #
The easiest way to install darcs 2.10.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
Dear Darcsers,
I'm planning to release Darcs 2.10.1 soon, which contains a few
bugfixes and dependency version bumps. If you want to help, please
get, build and test the 2.10 branch from over there:
* darcs clone:
http://darcs.net/releases/branch-2.10/
* zip download:
Hi Henning,
thanks for the kind comment!
Indeed the new diff algorithm is called patience diff and is
different and arguably more natural than the traditional myers diff.
In Darcs 2.10 you can compare both diff outputs in commands like
whatsnew or record by passing the flag --myers to get the
Nice! In further reading you could add this link:
http://darcs.net/Releases/2.10 instead of the GSoC links.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
: enable deep amending of history
(Ganesh Sittampalam)
- darcs pull --reorder: keep local-only patches on top of mainstream patches
(Ale Gadea, Ganesh Sittampalam)
- darcs dist --zip: generate a zip archive from a repository
(Guillaume Hoffmann)
- patch bundle contexts are minimized by default
The proposal is also on the website (not sure if the previous link is
publicly readable):
http://darcs.net/GSoC/2015-Conflicts-Handling-and-UI
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
An update on the darcs 2.10 release:
* we are close to it, the biggest bugs have been fixed.
* there are still unresolved bugs that are linked from the release
page, but the only blocker is 2438, which already has a patch that I
will accept friday if there is no objection (
(11)
issue822 Ernesto Rodriguez
~ - Generalized the IO Type for better error messages and exception handling
- http://bugs.darcs.net/issue822
issue2260 Ganesh Sittampalam
~ - skip internal patches when counting
- http://bugs.darcs.net/issue2260
issue2385 Guillaume Hoffmann
Dear darcs'ers,
this year's Summer of Code program starts son: by end of March,
student applications should be submitted to Google. We are probably
going to work again with students that have not contributed to darcs
before.
Since two students in my university are interested about it, I'd like
Hi Ben (and others),
sorry for being missing-in-action for so long, The combined effect of
end-of-year celebrations and summer holidays (here in the south
hemisphere) removed me from darcs development for a long time. Next
week I'll be able to come back to working on it.
I think we can aim at
://alegdarcs.blogspot.com.ar/2014/08/last-few-weeks.html
# Issues resolved (7)
issue1514 Guillaume Hoffmann
~ - send --minimize-context flag for send
- http://bugs.darcs.net/issue1514
issue1624 Marcio Diaz
~ - bucketed cache.
- http://bugs.darcs.net/issue1624
issue2153 Andreas
Please create a bug ticket and assign it to the 2.10 release :)
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Feature freeze has begun.
The code for the 2.10 release lives at:
http://darcs.net/releases/branch-2.10/
http://darcs.net/releases/branch-2.10/branch-2.10.zip
The bugs that should be fixed for the release can be found at:
http://tinyurl.com/lusjd38
This list of bugs still needs some triaging,
The absence of 'd' surprised me, but I guess the idea is that you want
a tag to tag 'almost everything' instead of 'almost nothing' in a
repository. Otherwise you create a patch with --ask-deps.
On a related note, indeed darcs amend [--unrecord] --ask-deps does
not work on tags, so this is a
It is fine as it is. Thanks Eric!
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Hi,
the patch index data structure will be present in darcs 2.10. It is
currently enabled by default in the development version of darcs
(since now 2 years).
We still have a problematic issue with it, that is, when cloning big
repositories, patch index creation consumes lots of memory. In some
Hi,
not before next november 3th, I'm kicking off the release process of
darcs 2.10 ( http://darcs.net/Development/ReleaseManagement ). That
is, I will clone our reviewed repository into a release-2.10
repository, and from then on the only stuff that will go in will be
bugfixes, optimizations and
The patch is now in screened (ie, the repository http://darcs.net).
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Then I think it is worth trying using -h for hash matching in 2.10.
I'll send a followup patch to the bundle
http://bugs.darcs.net/patch1177 soon.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Hi Gian Piero
now that `log` shows the hash of the patches, I would like to use it for
selecting patches as `log (or whatever) -p` is not much handy where there
are similar- or same-named patches. On the other hand, typing `--match
'hash` is boring, so I've added a `-H/--hash`[0] option that
The revert command creates a bundle in _darcs/patches/revert , you way
find the information you need in that file.
2014-08-17 6:26 GMT-03:00 Gian Piero Carrubba gpi...@rm-rf.it:
Use case:
I've a repo with patches A and B that are mutually exclusive. They aren't
conflicting, but both define a
Here's a patch to support network 2.6.
This only affects building when the HTTP library is used.
Works with:
cabal install -fhttp# to use network = 2.6
cabal install -fhttp -f-network-uri # to use network 2.6
Guillaume
support-network-2_6.dpatch
Description: Binary data
Here's a patch to enable matching on the short patch hash, so that
darcs 2.8.5 be more future-proof with regards to darcs 2.10.
enable-to-match-on-short-patch-hash-_future_proofing-wrt-darcs-2_10_.dpatch
Description: Binary data
___
darcs-users mailing
Looks sufficient to me.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
of 'bad sources'
- http://bugs.darcs.net/issue2364
issue2388 Owen Stephens
~ - check if inventories dir has been created
- http://bugs.darcs.net/issue2388
issue2394 Guillaume Hoffmann
~ - make optimize a supercommand
- http://bugs.darcs.net/issue2394
issue2396 Guillaume
`. This feature has now a more efficient implementation:
- http://hub.darcs.net/darcs/darcs-reviewed/patch/20140425060647-5ef8f
# Issues resolved (11)
issue851 Dan Frumin
~ - interactive mode for whatsnew
- http://bugs.darcs.net/issue851
issue1066 Guillaume Hoffmann
://bugs.darcs.net/issue642
issue2209 Jose Luis Neder
~ - Automatically detect replace
- http://bugs.darcs.net/issue2209
issue2319 Guillaume Hoffmann
~ - make changes non-interactive if fed to a pipe
- http://bugs.darcs.net/issue2319
issue2332 Guillaume Hoffmann
~ - ignore case
Haskell.org has been selected as mentoring organization by Google:
https://www.google-melange.com/gsoc/org/list/public/google/gsoc2014
Next deadline, March 10th for the beginning of the student application
period (ends March 21st).
___
darcs-users
Hi,
this year's google summer of code starts quite early. Student
application deadline is March 21st and Internship happens between May
19th and August 18th.
But most importantly now, organization application deadline is Feb
14th, that is, next Friday. Darcs will probably be part of the
I've sent http://bugs.darcs.net/patch and suggest the discussion
continues on darcs-devel / the patch tracker, if that's okay?
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
With regards to code duplication/divergence: I am proposing a minimal
feature that would work for most cases. That is, small size of code,
and without trying to be too clever (eg, the conflicts issue). So yes,
there would be some duplication, something like 150 lines.
darcs-bridge would still be
Hi,
I'd like to suggest that darcs should provide built-in, one-time
fast-export output.
Let me explain why we would want this, and why only the export direction:
- narrative for darcs 2.10: a built-in fast-export feature fits in a
narrative that presents darcs as a system that people can try
It may be a bad idea to do things differently just out of spite, but IMO a
good reason is enough to be different. Demanding absolute necessity
raises the bar a bit too high IMHO.
The abolute was probably too much, nevertheless if we agree on such
a guideline, we can get out of overlong
=20131028184855-5ef8f-ba33870773ad9ee010a470ac8536b5c7ae331b50
# Issues resolved (8)
issue346 Jose Luis Neder
~ - implement patience diff from bzr
- http://bugs.darcs.net/issue346
issue1828 Guillaume Hoffmann
~ - file listing and working --dry-run for mark-conflicts
- http
I like this, but making changes an alias for darcs log -i, thus avoiding
disruption for old-time darcsers.
I'm not sure about that, I believe all released versions changes
has always been non-interactive by default (your patch that made it
interactive only made its way into HEAD).
I'm thinking more and more that darcs should have a behaviour similar
to the most known VCS', unless there is some *absolute* necessity (by
design or design principle) to do another way.
The default expected use of changes (or log) is to show the history
of a repository, and we cannot really
Any thoughts about interactive changes by default?
darcs screened has had it since a few months. In some cases it
switches back to non-interactive (if fed to a pipe or given --count or
--xml-output, see http://bugs.darcs.net/patch1071 ).
Any regrets?
Guillaume
Short summary: darcs now uses a diff algorithm that generates more
human hunks, especially when editing code written in languages with
curly brackets.
I've recently pushed José Neder's patches (based on code written by
David Roundy) to the reviewed branch of darcs. See:
*
The point is to make all programs store their cache in the same
directory, so that users can just delete it when they run out of space
in their home directory.
When it comes to configuration files, I guess the idea of storing them
all in ~/.config is to 1) unclutter the home directory 2) make it
Ok but can we assume that users never come back to old versions of darcs?
If yes, then we can proceed to move everything:
* detect if ~/.darcs exists
* if yes, create ~/.config/darcs/, move everything under ~/.darcs/
except cache to ~/.config/darcs/
* if ~/.darcs/cache exists move
Hi,
I've just pushed to screened (ie http://darcs.net) a patch that makes
darcs use a more standard cache location (
http://bugs.darcs.net/patch1080 ):
This patch basically makes darcs using ~/.cache/darcs/ instead of
~/.darcs/cache. Unless $XDG_CACHE_HOME is set, in which case it
will use
HI,
Three of these files actually contain conflict markers, but the third one
(./src/seq/seq_if.c) does not. Even so, most of the changes that I expected
to see in the file are not there, so it seems Darcs acted as if I had said
--no-mark-conflicts.
Could it be that the conflict with
Thanks for testing!
I wonder if we should do something similar with ~/Library/Preferences
You mean moving the contents of ~/.darcs to
~/Library/Preferences/darcs, and also ~/.darcs to ~/.config/darcs
under Linux ?
Darcs should do the move automatically then. Contrary to the cache,
the
Hi Iva,
sorry for the late response!
The manual of darcs is going to change a lot for the next release (2.10).
The one that is available on-line corresponds to darcs 2.8, it is
generated from latex files that used to be in darcs' repository. As it
got more and more out of date (with respect to
issue2321 Jose Luis Neder
~ - when no patch name given, directly invoke text editor
- http://bugs.darcs.net/issue2321
# Patches applied (20)
2013-06-09 Guillaume Hoffmann
~ - make nano the default text editor instead of vi
2013-06-20 BSRK Aditya
~ - Resolve issue2250: tabbing
To clarify the current proposal, I renamed the issue on the bug
tracker to when no patch name given, directly invoke text editor.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
What I recollect from your message, however, is that you point out a
general issue of Robustness with darcs, and I agree with this.
Especially robustness as perceived by casual users. I personally find Darcs
quite reliable in my day-to-day experience.
Yes, that's exactly the issue. As
Congratulations to BSRK Aditya and José Neder, our Google Summer of
Code students of 2013!
They will work until end of September on the following projects:
* http://darcs.net/GSoC/2013-Darcsden ( BSRK Aditya, mentored by Ganesh )
* http://darcs.net/GSoC/2013-BetterRecord ( José Neder, mentored
Hi Ben,
First, since you are aware that we all have little time to dedicate to
darcs, you should try to send shorter, more synthetic mails.
What I recollect from your message, however, is that you point out a
general issue of Robustness with darcs, and I agree with this.
The problems you
Alright, I believe we want to make this change: make that darcs record
without -m flag directly launches the long description editor.
This would make darcs behave similarly to most other VCS. Definitely a
probably-easy change to do.
___
darcs-users
Hi everyone,
Marcio told me that he finally will not be able to apply to GSoC this year :-(
The good news is that we have an application that has already received
a good amount of feedback (from Owen but also from me offline), and
that can be reused by anyone who is interested. So please go
`amend-record`:
- http://lists.osuosl.org/pipermail/darcs-users/2013-March/026838.html
# Issues resolved in the last week (1)
issue2274 Guillaume Hoffmann
~ - create patch index only with commands that take a lock
- http://bugs.darcs.net/issue2274
# Patches applied in the last
~ - don't allow remote operations to copy the rebase patch
- http://bugs.darcs.net/issue2282
issue2287 Radoslav Dorcik
~ - obliterate -O doesn't overwrite existing file.
- http://bugs.darcs.net/issue2287
# Patches applied in the last week (77)
2013-02-21 Guillaume Hoffmann
What about we finally make `darcs changes` interactive by default?
And (as suggested by Florent on IRC) map 'y' to 'p' (use `less`)
instead of 'v' as of now.
___
darcs-users mailing list
darcs-users@darcs.net
Interesting!
I'm leaving for the sprint now, but do you think you can write a nice
README.md file that would describe the installation steps, and the
current / planned features of your project ?
thanks.
___
darcs-users mailing list
# News and discussions
1. Confirmed: the next Hacking Sprint will be in IRILL, Paris on
February 15, 16 and 17:
- http://darcs.net/Sprints/2013-02
- http://www.irill.org/
2. Darcs HEAD has been fixed to work with GHC 7.6 without encoding
bugs, go ahead and try it!
-
After more chatting and asking, it has been confirmed that the sprint
will take place on February 15-17, in IRILL, Paris!
see you there
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
After some chatting on IRC we concluded that the next sprint will be:
* on February 22-24
* in Paris or Southampton or (if I can get in contact with people from
there) Lille.
Let's give us one more week to see the options of place.
In the meantime, if more people want to participate, just
Hi,
I'll be in Europe next February and (beginning of) March. Maybe we
could arrange a sprint during this period?
The event can be hosted in Nancy, France [1] (where I'll be staying)
or we can do it again at the IRILL in Paris, like in spring of 2011
[2].
My possible dates would be in February
://darcs.net
3. Eric Kow documented the workflow of having a group of users working with
the same repository:
- http://lists.osuosl.org/pipermail/darcs-users/2012-June/026523.html
- http://darcs.net/Using/GroupRepo
# Issues resolved in the last week (3)
issue2193 Guillaume Hoffmann
Hi Eric,
if you know how to make darcs.net redirect to the wiki and keep on
serving the screened and reviewed repositories at the same place, why
not. Otherwise we will have to wait until we have a working
den.darcs.net and more all of our repos over there (which I think
would be something we
I've converted the 'thanks' and 'donations' pages as wiki pages. I
don't think we need to make redirections from their old URL to these
wiki pages. In the 'donation' page I couldn't copy the javascript
piece of code for google checkout, but donating with this widget seems
to work anyway.
I can't
For those who haven't followed, we are trying to move some things out
of darcs' darcs repository. One of these things is the website
homepage, that we're trying to embed into the wiki. We dicussed the
topic on darcs-devel (the topic was tackled among many other things,
see Eric's answer to the
Guillaume Hoffmann
~ - haddock for fixUrl and fix 2 haddocks
- make darcs apply work with url
- kill footnotes in manual and uninformative command-overview paragraph
2012-05-18 Michael Hendricks
~ - Fix show-authors test on OS X
2012-05-16 Owen Stephens
~ - Tidy/Style
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
A few memory allocation figures obtained with +RTS -s for two cases
(recent patch and old patch):
* patch kill footnotes (latest):
2.8
287,535,128 bytes allocated in the heap
59,356,640 bytes copied during GC
14,969,680 bytes maximum residency (9 sample(s))
342,752
I've updated the wiki page which url is now
http://wiki.darcs.net/Using/Test .
g.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
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
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
- 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
and apply
* http://bugs.darcs.net/issue1228
issue2145 Guillaume Hoffmann
* enable j key in amend-record
* http://bugs.darcs.net/issue2145
Patches applied in the last week (20)
-
2012-01-22 Owen Stephens
- Fix amend-unrecord test, broken by last-regrets
1 - 100 of 247 matches
Mail list logo