Mark Stosberg wrote:
Here's the report I made for the Darcs 2 release-critical issues. I used the
feature to save it so it appears in Your Queries in the sidebar.
It shows that 2 of the 7 items on the list are resolved now.
http://bugs.darcs.net/[EMAIL
On Thu, Feb 21, 2008 at 10:57:55AM +, Simon Marlow wrote:
Mark Stosberg wrote:
Here's the report I made for the Darcs 2 release-critical issues. I used
the feature to save it so it appears in Your Queries in the sidebar.
It shows that 2 of the 7 items on the list are resolved now.
How about 699 [darcs2 cannot check the ghc-darcs repository] ? Unless I'm
doing something completely bogus (don't think
so), darcs2 has developed a new performance problem recently.
In the sense that it looks like a regression, it's a candidate.
Mark
--
topic: +FixForDarcs20
David Roundy wrote:
On Thu, Feb 21, 2008 at 03:42:42AM -, Mark Stosberg wrote:
I decided I don't like using Superseder to track dependencies for release,
because there's not way to see a report of all of these tickets, so we can
easily review what they are, and what the status is. So
I decided I don't like using Superseder to track dependencies for release,
because there's not way to see a report of all of these tickets, so we can
easily review what they are, and what the status is. So instead I'm tagging all
of the issues with the FixForDarcs20 tag, so we can make such a
I'm assigning this bug to myself, just so it's easier for me to see what's
listed here. I appreciate the work you've been doing Mark on marking bugs as
release-critical in this way. And would appreciate similar work by others!
David
--
assignedto: - droundy
Adding issue568 as a dependency. It's apparent regression in the unstable branch
with the title of wrong report of Skipped 6 patches due to dependencies.
--
superseder: +wrong report of Skipped 6 patches due to dependencies
__
Darcs bug tracker [EMAIL
bugs:
Adding new recommended dependency: disabling bytestring by default for now
to
avoid bus errors.
bus errors using bytestring by default? Has the cause of this been
identified?
___
darcs-devel mailing list
darcs-devel@darcs.net
Hi Don,
bus errors using bytestring by default? Has the cause of this been
identified?
It's an error I got trying to apply a patch which was darcs sent from
a Windows box
http://bugs.darcs.net/issue697
The repository is the wxhaskell one (actually the patch has already
been applied, so
Nominating bug with pre-gzipped files as something to look into before the Darcs
2 release. That's issue673.
--
superseder: +hash failure with hashed and darcs-2 format
__
Darcs bug tracker [EMAIL PROTECTED]
http://bugs.darcs.net/issue659
I'm nominating issue585 to be addressed for the Darcs 2 to be released. This is
a bug in convert where flattening mergers changes the dependency structure and
can make old tags inaccessible.
--
superseder: +optimize --reorder = Failure commuting patches in commute_by
called by gpit!
I nominate issue579 to be fixed for the Darcs 2 release. The issue title is:
Darcs2: changes shows revised history
--
superseder: +Darcs2: changes shows revised history
__
Darcs bug tracker [EMAIL PROTECTED]
http://bugs.darcs.net/issue659
On Thu, Feb 07, 2008 at 05:56:52PM -, Mark Stosberg wrote:
Based on the bug tracker activity, my sense is that Darcs 2 is already better
than 1.0.9, with no significant regressions that I'm aware of.
Another major regression is the slowdown of record when adding many
files, which was
New submission from Mark Stosberg [EMAIL PROTECTED]:
This ticket is created to track the release of Darcs 2.0. Other bugs or features
that are blocking the release can associated as superceders. When those are
all resolved, the release should happen.
Based on the bug tracker activity, my sense
14 matches
Mail list logo
