[darcs-devel] darcs patch: boring += autom4te.cache/

2006-01-30 Thread Kirill Smelkov
Mon Jan 30 10:14:16 MSK 2006 Kirill Smelkov [EMAIL PROTECTED] * boring += autom4te.cache/ -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 New patches: [boring += autom4te.cache/ Kirill Smelkov [EMAIL PROTECTED]**20060130071416] { hunk ./RepoPrefs.lhs 125 - - (^|/)Thumbs\\.db$]

[darcs-devel] [issue118] [EMAIL PROTECTED] didn't work for me

2006-01-30 Thread David Glasser
New submission from David Glasser [EMAIL PROTECTED]: I sent a message to [EMAIL PROTECTED] on January 29th (subject: test failure in pull.pl on AFS) and got no response, nor did an issue show up here. (I later created that issue here through the web interface.) -- messages: 443 nosy:

[darcs-devel] [issue120] I wish I could do darcs pull --allow-conflicts.

2006-01-30 Thread Zooko
New submission from Zooko [EMAIL PROTECTED]: I need this for my two-way-sync script between darcs and svn. Currently I work around it by doing darcs pull ; darcs revert --all to erase the conflict markers. -- messages: 445 nosy: droundy, tommy, zooko status: unread title: I wish I

[darcs-devel] Late with patching...

2006-01-30 Thread Juliusz Chroboczek
Dear all, From the state of my mailbox, it looks like I'm at least 2 weeks behind in maintaing the unstable branch. Please bear with me -- I'm a little bit late with work. Sorry for that, Juliusz ___

[darcs-devel] Re: wxDarcs and withRepoLock

2006-01-30 Thread Eric Kow
On 29 janv. 06, at 01:06, Eric Kow wrote: But one horrible thing that happens is that the record command never gets around to releasing its repository lock, even if you close the Record window (2). It doesn't matter if you actually record something or if you cancel. Both options leave the