bugs: we run into darcs bugs other than the conflict/merging bug on
a regular basis.
This is true, but I think things are improving.
Yes they are. I would say that the bug tracker has about every
significant bug in it. Darcs 2 addresses many major bugs, and our open
bug count is lower than
We know what happens when a process is spawned and run -- the only
remaining uncertainty is what the buildbot does with the stderr,
stdout, and stdin pipes of the child process. Here is the relevant
source code:
http://buildbot.net/trac/browser/buildbot/slave/commands.py?rev=491#L311
The
On Sat, 8 Mar 2008, zooko wrote:
If I run this bash command line on Mac OS 10.4:
$ perl shell_harness rollback.sh
Then it runs the rollback.sh test and quickly finishes successfully.
If I run this command-line:
$ python -c 'import os;os.system(perl shell_harness rollback.sh)'
Which
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
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
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!
From reading this bug history, it is resolved-in-unstable, and Tommy is in
the
process of porting this fix to darcs-stable, so that it can be resolved there,
too.
--
status: need-eg - resolved-in-unstable
__
Darcs bug tracker [EMAIL PROTECTED]
Lynagh [EMAIL PROTECTED]
285 Mark Stosberg [EMAIL PROTECTED]
267 Tommy Pettersson [EMAIL PROTECTED]
217 Juliusz Chroboczek [EMAIL PROTECTED]
168 Eric Kow [EMAIL PROTECTED]
142 Eric Kow [EMAIL PROTECTED]
101 [EMAIL PROTECTED]
Also, the result is easily parsed between
On Thu, 14 Feb 2008, Jason Dagit wrote:
I just tried to 'darcs send' to the unstable repository but I get this:
$ darcs send http://darcs.net/repos/unstable
darcs failed: Not a repository: http://darcs.net/repos/unstable
(Failed to download URL
On Thu, 7 Feb 2008, Allan Lyons wrote:
Hi,
On http://wiki.darcs.net/DarcsWiki/PatchPlugins there is discussion
about different atomic patch types. The page points out that test
files are different from binary files and suggests that those two cases
might be handled adequately. It also
You can also always record a patch before you pull, and then unrecord the patch
afterwards.
I'm tentatively marking this as resolved-in-unstable, since I consider these
options sufficient. Another contributor is welcome to re-open the issue.
Mark
--
nosy: +amber, markstos -amber
New submission from Mark Stosberg [EMAIL PROTECTED]:
To reproduce:
darcs init --hashed --repodir=u2
cd darcs-unstable-repo
time -p darcs push -a --no-set ../u2
Resolving conflicts 5/27
Apply failed!
real 862.99
user 731.10
sys 3.98
###
Darcs takes a very long time and then results in apply
Per David's comments, this is considered resolved-in-unstable, although it can
still be triggered with darcs-2 when run against repos that were originally
created with darcs 1 and the old repo format.
--
status: duplicate - resolved-in-unstable
__
Darcs
New submission from Mark Stosberg [EMAIL PROTECTED]:
I'm sorry if you got mail about this. You can ignore it.
--
messages: 3300
nosy: beschmi, droundy, kowey, markstos, tommy
priority: bug
status: chatting
title: Testing RoundUp Cli
__
Darcs bug tracker
With no further feedback from the requestor in over six months, I'm marking this
as wont-fix for. (More like presumed-dead). No one else has reported a dupe
during that time.
--
nosy: +eivuokko, jaredj, markstos, rgm, wglozer
status: chatting - wont-fix
topic: +Windows
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
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
New submission from Mark Stosberg [EMAIL PROTECTED]:
I'm marking this as urgent because darcs reports this as a bug itself, and it's
rather easy to trigger with the current darcs-unstable.
#!/bin/sh
IFS='';
export IFS;
EMAIL=tester;
export EMAIL;
set -ev;
rm -rf tmp;
darcs init --darcs-2
I started on this about three years ago. You are welcome to re-use my work from
then:
http://lists.osuosl.org/pipermail/darcs-devel/2005-March/001524.html
http://mark.stosberg.com/darcs_hive/darcs_speed_test/
Mark
--
nosy: +markstos
status: chatting - deferred
title: automated
I have also accidentally done a plain mv numerous times when I should have
done a darcs mv. My suggestions fo r implementing this would be:
- darcs mv with no arguments could be interactive...it would look for likely
moves and then prompt the user to confirm each one. I suppose could you also
I agree with the revised wish that darcs send -o also provide the e-mail of
the remote repo, realizing the language would need to be different...it would
just be factually reporting the address, insteading of claiming that an e-mail
has been sent there.
--
nosy: +markstos
status:
Fri Feb 1 21:48:05 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue469: test that _darcs/prefs/binaries matches against full path
Sat Feb 2 10:01:09 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* improved test for binaries: We now have both a positive and negative test
New patches
Sat Feb 2 04:51:22 EST 2008 Trent W. Buck [EMAIL PROTECTED]
* Add functional sh test for issue458.
Sat Feb 2 10:59:04 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue458: move currently failing test to bugs/
New patches:
[Add functional sh test for issue458.
Trent W. Buck [EMAIL
Sat Feb 2 05:38:16 EST 2008 Trent W. Buck [EMAIL PROTECTED]
* Add functional sh test for issue496.
Sat Feb 2 11:28:28 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue496: move failing test to ./bugs
New patches:
[Add functional sh test for issue496.
Trent W. Buck [EMAIL PROTECTED
Sat Feb 2 22:15:17 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue572: Add Some .waf files to the default boring list.
New patches:
[issue572: Add Some .waf files to the default boring list.
Mark Stosberg [EMAIL PROTECTED]**20080203031517] hunk ./src/Darcs/Repository/Prefs.lhs 175
New submission from Mark Stosberg [EMAIL PROTECTED]:
This wish was found in the Debian Bug Tracker, submitted by 'luca', who I'm
adding to the 'nosy' list:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462330
###
The Debian Common Lisp Team [2] would like to receive a mail every time
a new
New submission from Mark Stosberg [EMAIL PROTECTED]:
The tab completion for darcs2 looks broken because the current line gets
overwritten.
This could be solved by adding --quiet in the right place in
tools/darcs_completion, assuming all commands take a --quiet option.
However, as you can see
Wed Jan 30 23:23:13 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue366: test when unrevert reports a bug
New patches:
[issue366: test when unrevert reports a bug
Mark Stosberg [EMAIL PROTECTED]**20080131042313] {
addfile ./bugs/unrevert_cancel.sh
hunk ./bugs/unrevert_cancel.sh 1
+#!/bin/sh
There is now a progress reporting framework in the unstable branch.
--
nosy: +markstos
status: chatting - resolved-in-unstable
__
Darcs bug tracker [EMAIL PROTECTED]
http://bugs.darcs.net/issue498
__
On Mon, 28 Jan 2008, Andreas wrote:
I've also taken the time to test the new darcs2 and I think I may have found a
problem.
I have 2 repositories A and B. B is bigger than A. It has all the patches from
A and some more.
Now I independently converted both repositories to darc2 format - A2
Sat Jan 26 10:44:44 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Test infrastructure improvement: Add debug mode to Perl test scripts.
Set this to see the output of every 'darcs' call made through this script:
DARCS_DEBUG=1 ./bin/prove -v add.pl pull.pl
New patches:
[Test infrastructure
Sat Jan 19 19:58:50 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* remove now-unused perl_harness
Sat Jan 19 20:05:53 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Remove more unneeded --author flags in the Perl test scripts, because the
harness takes care of them
Wed Jan 23 20:35:52 EST 2008
Michael,
Thank for the additional testing. I know the download/compile/test cycle can be
time consuming. Based on your report, I'm marking this as
resolved-in-unstable.
The numbers you are seeing are part of a new progress reporting framework It
is still getting the kinks worked out, but is
Sun Jan 27 00:38:11 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue154: regression test for pull with a directory removal conflict
New patches:
[issue154: regression test for pull with a directory removal conflict
Mark Stosberg [EMAIL PROTECTED]**20080127053811] {
addfile ./tests
Wagner Ferenc wrote:
David Roundy [EMAIL PROTECTED] writes:
On Thu, Jan 24, 2008 at 09:56:18AM +0100, Nicolas Pouillard wrote:
What about automatically launching a pager ($PAGER) when the output is a
tty?
Note: That's git default
I think this is probably the better option.
It
Is there anyone on darcs-devel that could help with what looks an easy bug fix
for Windows? See the issue tracker link online for more context:
On Thu, Jan 24, 2008 at 02:32:01 -, Mark Stosberg wrote:
let opts = fix_context orig_opts
fix_context o@(Context ('/':_):_) = o
What about automatically launching a pager ($PAGER) when the output is a tty?
That would help because it would leave the basic help visible at the top
of the screen. And I suppose I could quit the pager before scrolling
down to view the advanced text.
There definitely other uses of darcs
Wed Jan 23 20:38:56 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue608: a new test for 'mv', following Zooko's bug report
New patches:
[issue608: a new test for 'mv', following Zooko's bug report
Mark Stosberg [EMAIL PROTECTED]**20080124013856] {
hunk ./tests/mv.pl 6
-use Test::More tests
Tue Jan 22 18:54:35 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* update some ChangeLog entries to also credit those who contributed through
bug reporting, test writing or feedback.
Tue Jan 22 19:04:17 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* update restrictive perms test to run
New submission from Mark Stosberg [EMAIL PROTECTED]:
I think the --debug, --debug-verbose and --timings flags should be moved out of
the regular help and into the Advanced Help. Like many of the other advanced
options, they are not related to the specific command and are common for many
commands
Sat Jan 19 22:56:51 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Major Perl test suite clean-up.
The primary purpose of this patch was make sure all the tests are
executed in
randomly named directories, which allows us to run Perl tests in
parallel,
without
David Roundy wrote:
On Sat, Jan 19, 2008 at 02:21:36AM -, Mark Stosberg wrote:
My co-worker uses Mail.app and can't detach darcs patches, so my team is
directly affected by this.
This sounds like it's an issue of darcs generating correct MIME emails,
rather than parsing them
Assigning to myself as test-script cleanup issue.
--
assignedto: - markstos
nosy: +markstos
status: resolved - chatting
__
Darcs bug tracker [EMAIL PROTECTED]
http://bugs.darcs.net/issue595
__
David beat me to the test-cleanup work. (Thanks!). I'm going to consider this
resolved for now, since we now lack a test case which triggers an unresolved
problem.
--
status: chatting - resolved
__
Darcs bug tracker [EMAIL PROTECTED]
New submission from Mark Stosberg [EMAIL PROTECTED]:
clanehin reported this on IRC, but I was getting the same failures with 6.6.1,
but hadn't reported them yet for fear it was something unique to my environment.
It seems they might be a real issue. The tests are indicating that in 5 cases,
date
Sun Jan 20 20:42:46 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue562: update Perl test infrastructure so all Perl tests pass with a
space in the path to darcs
Sun Jan 20 22:11:03 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue562: Update the .sh scripts and the shell_harness so
New submission from Mark Stosberg [EMAIL PROTECTED]:
Trent Buck wondered on IRC tonight of optimize --relink was broken in Darcs2.
I observed that we don't have an automated test for --relink, although there
is a tests/optimize.pl already. It would be nice to have one.
[21:15] twb Is darcs
Sun Jan 20 22:40:28 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue600: a test for optimize --relink
New patches:
[issue600: a test for optimize --relink
Mark Stosberg [EMAIL PROTECTED]**20080121034028] {
addfile ./bugs/optimize_relink.sh
hunk ./bugs/optimize_relink.sh 1
+#!/bin/sh
Fri Jan 18 20:42:20 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue595: A test when darcs fails with a possibly-avoidable permissions
error
New patches:
[issue595: A test when darcs fails with a possibly-avoidable permissions error
Mark Stosberg [EMAIL PROTECTED]**20080119014220] {
addfile
I looked into this some.
The current meager mail parsing happens in Darcs/Email.hs in the read_mail
routine around line 122.
However, I suspect it would be fairly easy to take advantage of one of the
Haskell MIME parsing libraries which have appeared since the darcs project
started. For
Fri Jan 18 22:27:26 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Adding File-Slurp-.12 perl module to tree, to add with testing.
It is licensed under the GPL, and includes easy functions
to read, write and append to files.
Fri Jan 18 22:45:31 EST 2008 Mark Stosberg [EMAIL
Fri Jan 18 22:27:26 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Adding File-Slurp-.12 perl module to tree, to add with testing.
It is licensed under the GPL, and includes easy functions
to read, write and append to files.
Fri Jan 18 22:45:31 EST 2008 Mark Stosberg [EMAIL
Sat Jan 19 00:31:11 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue174: behave better when we want to obliterate a patch that comes
before a tag. (a test)
New patches:
[issue174: behave better when we want to obliterate a patch that comes before a tag. (a test)
Mark Stosberg [EMAIL
Last night I switched the bug tracking system from using the slow
anydbms backend to a faster PostreSQL backend.
This morning I noticed some e-mail communications to the bug tracker
were appearing in duplicate (but not others):
http://bugs.darcs.net/issue590
http://bugs.darcs.net/issue589
Thu Jan 17 21:06:34 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Issue395: avoid single letter patch names in the test suite.
Thu Jan 17 22:02:41 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* use --ignore-time in tests instead of sleep, for faster, more reliable
results
Thu Jan 17 22:16:06
I have now updated the homepage of http://bugs.darcs.net to be more
useful.
It now runs a more useful query for the bugs to display by default,
eliminating bugs that are in any state of being resolved, wont-fix,
etc. This should make it easier to find bugs that actually need
attention.
Also,
New submission from Mark Stosberg [EMAIL PROTECTED]:
Just testing.
--
messages: 2541
nosy: beschmi, droundy, kowey, markstos, tommy
priority: urgent
status: unread
title: Testing new PostgreSQL backend for the bug tracker. Please Ignore
__
Darcs bug
On Mon, 14 Jan 2008, zooko wrote:
$ darcs pull -v -v -v
Did you try darcs pull --debug as alternative?
I think that may have the verbose output you are looking for.
Our docs say that verbose produces more information, but exactly what
that information is defined per sub-command.
In the case
Sat Jan 12 21:55:55 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* A test for unrecording checkpoint tags, inspired by issue517
New patches:
[A test for unrecording checkpoint tags, inspired by issue517
Mark Stosberg [EMAIL PROTECTED]**2008011302] {
addfile ./tests/checkpoint.sh
hunk ./tests
Wed Jan 9 20:02:18 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* fix potentially troublesome 'rm -rf temp*' commands in test scripts, which
could have deleted more than intended.
Wed Jan 9 21:30:44 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* clean up test script header...no functional
Sat Jan 12 18:31:51 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* Issue81: Add test which shows that old and hashed formats consider
dopplegangers a conflict, but the darcs-2 format doesn't.
New patches:
[Issue81: Add test which shows that old and hashed formats consider dopplegangers
--
http://mark.stosberg.com/
New patches:
[issue347 - document that single quotes should be used in .darcs/defaults
Mark Stosberg [EMAIL PROTECTED]**20080101164428] {
hunk ./src/Darcs/ArgumentDefaults.lhs 46
+If the value has spaces in it, use single quotes, not double quotes, to surround
After just trying to pull the lasted patches and make on Ubuntu Gutsy
with GHC 6.6.1, I get this result:
src/Darcs/Patch/Patchy.lhs:87:14:
Kind error: `p' is applied to too many type arguments
In the type `p x y'
In the type `p x y - p y x'
In
New submission from Mark Stosberg [EMAIL PROTECTED]:
This bug report can be illustrated with the shell script uploaded through
issue578.
The result is that after going through the Steve and Monica example from
DarcsTwo,
darcs changes reports that one conflicting patch contains no content
Sun Jan 6 23:43:16 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* add ChangeLog entry for HTTP Pipelining support
Tue Jan 8 22:23:46 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue567: regression test for moving a file to the same location as itself
New patches:
[add ChangeLog entry
Tue Jan 8 23:45:00 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* regression test for issue406
New patches:
[regression test for issue406
Mark Stosberg [EMAIL PROTECTED]**20080109044500] hunk ./tests/partial.sh 50
+
+# This is a regression test for issue406
+$DARCS tag -A x --checkpoint
Mon Jan 7 19:57:10 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* correct apparent typo in test.
The fix made more sense than the former behavior of comparing a file to
itself.
Mon Jan 7 20:00:43 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue55: document that darcs handles some
Sun Jan 6 23:43:16 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* add ChangeLog entry for HTTP Pipelining support
New patches:
[add ChangeLog entry for HTTP Pipelining support
Mark Stosberg [EMAIL PROTECTED]**20080107044316] {
addfile ./changelog.in/entries/issue377
hunk ./changelog.in/entries
Mark Stosberg [EMAIL PROTECTED] added the comment:
I recommend resolving this as wont-fix. I believe darcs get --to-patch is a
fine solution to the stated problem, and is much like the SVN solution. SVN
solution also uses two copies of the tree (one in the server and one in the
client
Tue Jan 1 11:44:28 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue347 - document that single quotes should be used in .darcs/defaults
New patches:
[issue347 - document that single quotes should be used in .darcs/defaults
Mark Stosberg [EMAIL PROTECTED]**20080101164428] {
hunk ./src/Darcs
Sat Jan 5 13:17:51 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* refactor: improve style and portability of pull.pl test script.
Many direct system calls were eliminated. No functional changes.
New patches:
[refactor: improve style and portability of pull.pl test script.
Mark Stosberg
Sat Jan 5 13:30:27 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* typo fix on GNUmakefile comment
Sat Jan 5 13:36:41 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* minor white-space and code style improvements
New patches:
[typo fix on GNUmakefile comment
Mark Stosberg [EMAIL PROTECTED
Sat Jan 5 23:55:48 EST 2008 Mark Stosberg [EMAIL PROTECTED]
* issue526: improve Perl test suite.
- better compatibility when path to darcs includes a space
- better portability by eliminating some system calls
- general style improvements
New patches:
[issue526: improve
Mark Stosberg [EMAIL PROTECTED] added the comment:
Where is this place where this occurs? Just running darcs revert with 1.0.9
looks like this:
$ darcs revert
hunk ./1.t 1
+b
Shall I revert this change? (1/?) [ynWsfqadjkc], or ? for help:
###
...it is already singular.
--
nosy
New submission from Mark Stosberg [EMAIL PROTECTED]:
Darcs should have 'darcs remove -r' to complement 'darcs add -r'
The use case: I ran darcs add -r only to find that it added many files I
intended to be boring. I wanted to undo that action and try again. darcs remove
-r would do
New submission from Mark Stosberg [EMAIL PROTECTED]:
When I do darcs optimize --help, the docs for --checkpoint say simply:
create a checkpoint file
Defining a checkpoint in terms of itself is not so helpful. I suggest instead:
prepare repo for use with darcs get --partial
Following the Perl 6 project, I see reports that pugs is
noticeably faster when compiled with GHC 6.6 vs. 6.4.
I was wondering if some of the slower operations of darcs might also
be faster when compiled with a newer GHC or if the issues are primarily
algorithmic, making this difference
Thomas Counsell wrote:
Hello
On 21 Aug 2006, at 05:33, Eric Y. Kow wrote:
Should we maybe tone down the Smart bit?
Maybe something like Flexible
Flexible when applied to software can mean needs lots of configuration
or Simple... Isn't that what we're
trying to get at?
Simple can mean
Sun Aug 20 15:14:15 EDT 2006 Mark Stosberg [EMAIL PROTECTED]
* overhaul the darcs.net front page.
The themes to this change are:
- Focus on the key benefits of darcs:
Distributed. Interactive. Smart.
- Recognize that the wiki is the central resource,
and remove some
Mark Stosberg wrote:
Sun Aug 20 15:14:15 EDT 2006 Mark Stosberg [EMAIL PROTECTED]
* overhaul the darcs.net front page.
The themes to this change are:
- Focus on the key benefits of darcs:
Distributed. Interactive. Smart.
- Recognize that the wiki is the central resource
Here's the description of what the proposed new option does:
+To scrutinize each patch before recording it in the local repository,
+supply a command with \verb!--check-patch!.
It sounds rather similar to what --test does, although I can see the
intent is different.
The docs referenced
David Roundy wrote:
I've put up a draft of some of the new conflict-handling ideas at
http://darcs.net/conflicts/paper/paper.pdf
From the sidelines it seems promising. I'm glad that it seems like
there's been a significant breakthrough with the conflicts issue.
I'm slightly concerned about
New submission from Mark Stosberg [EMAIL PROTECTED]:
'darcs add' will automatically add a new directory when adding a file, but
'darcs
record' doesn't recognize the file:
$ darcs addnew/dir/file.txt
$ darcs record new/dir/file.txt
darcs record new/dir/file.txt
Recording changes
Hello,
I just want to report a successful build and make test of darcs in my
environment:
darcs 1.0.8pre1
ghc 6.2.2
FreeBSD 4.10
Perl 5.8.0
Thanks for your continued work on this project. It's become hard to
imagine developing without it!
Mark
Wed Nov 23 19:59:29 EST 2005 Mark Stosberg [EMAIL PROTECTED]
* some TODO tests for darcs --commands [Issue9]
These tests expose two bugs:
- cd /; darcs --commands doesn't work
- darcs --commands outside of repos reports too many commands, like get.
New patches:
[some TODO tests
New submission from Mark Stosberg [EMAIL PROTECTED]:
I would like to include a MANIFEST file automatically when doing 'darcs
dist'
This doesn't work, because the _darcs directory is not present at
predist time:
darcs setpref predist darcs query manifestMANIFEST
Since I can't think of a good
New submission from Mark Stosberg [EMAIL PROTECTED]:
( This is an import of bug #165 from the old system. There is still a TODO
test for it in pull.pl, indicating it is still present. )
There is a workaround: Create a temp repo with 'darcs get
--to-patch roll_me_back' and rollback the patch
On Wed, Dec 14, 2005 at 11:48:54PM +0100, Juliusz Chroboczek wrote:
+ single repository! Also, running amend-record while another user is
pulling\n++
+ from the same repo may cause repository corruption.\n
Is that true? Why?
I didn't write that sentence, I only moved it from one part
Tue Dec 13 09:05:23 EST 2005 Mark Stosberg [EMAIL PROTECTED]
* make dangers and recommended use of Amend clearer in the docs.
I think it's important to be clearer about when it's appropriate to use
'amend',
so I moved some notes into the short and mid-length help texts.
New patches
New submission from Mark Stosberg [EMAIL PROTECTED]:
I got this error today with Darcs 1.0.4:
darcs failed: user error (Error applying patch to working dir:
createDirectory: already exists (File exists))
This may have left your working directory an inconsistent
Wed Oct 12 15:43:04 EST 2005 Mark Stosberg [EMAIL PROTECTED]
* add files starting with .* to default boring list. Dreamweaver uses these.
Wed Nov 23 19:11:49 EST 2005 me
* newdir
Wed Nov 23 19:13:27 EST 2005 me
* newdir
Wed Nov 23 19:18:19 EST 2005 me
* newdir
Wed Nov 23 19:20:13
On 2005-10-21, Mark Stosberg [EMAIL PROTECTED] wrote:
Hello,
I just tried a pull with darcs 1.0.3, and it failed it some way
that produced a ton of patch data dumped to the screen. (So much in fact
that I couldn't scroll back to see what the actual error was).
I switched to a 1.0.4rc2
Hello,
I just tried a pull with darcs 1.0.3, and it failed it some way
that produced a ton of patch data dumped to the screen. (So much in fact
that I couldn't scroll back to see what the actual error was).
I switched to a 1.0.4rc2 binary, and it completed the pull without an
error. However,
On 2005-10-13, Juliusz Chroboczek [EMAIL PROTECTED] wrote:
I had a typo in my patch name, so I tried to unrecord it and got this
message:
Fail: failed to read patch in get_extra:
Fri Feb 4 07:37:49 EST 2005 David Roundy [EMAIL PROTECTED]
* bump version number to 1.0.2 (at
Tue Sep 27 08:18:47 EST 2005 Mark Stosberg [EMAIL PROTECTED]
* simplify docs-- why CVS is in the boring file is self-evident.
New patches:
[simplify docs-- why CVS is in the boring file is self-evident.
Mark Stosberg [EMAIL PROTECTED]**20050927131847]
{
hunk ./RepoPrefs.lhs 86
On 2005-09-09, Tommy Pettersson [EMAIL PROTECTED] wrote:
On Fri, Sep 09, 2005 at 03:17:47AM +, Mark Stosberg wrote:
I tried this and got the same result:
DARCS_DONT_ESCAPE_ISPRINT=0 DARCS_DONT_ESCAPE_8BIT=0
DARCS_DONT_ESCAPE_EXTRA=0
DARCS_DONT_ESCAPE_TRAILING_SPACNT_ESCAPE_ANYTHING=0
On 2005-08-02, via RT [EMAIL PROTECTED] wrote:
The current interface of darcs changes and darcs annotate includes
various options that affect the criteria of patch selection and the form
of output. These options seem insufficient for most people's needs of
querying patches, and should
1 - 100 of 109 matches
Mail list logo
