Trent W. Buck trentb...@gmail.com added the comment:
Eric Kow wrote:
Just a quick question for you. Is it OK if we change the EXAMPLE.sh
template to just Public domain instead of the BSD3 boilerplate?
Assuming you're asking for my permission as the author: yes.
If you'are asking whether
Trent W. Buck trentb...@gmail.com added the comment:
Juliusz Chroboczek wrote:
I sent the papers to the FSF. I never received a reply.
The process was rather unpleasant (I couldn't just sign a document
saying I assign all alienable rights to vc-darcs.el to the FSF, as
I can do with e.g
Guillaume Hoffmann guilla...@gmail.com writes:
ssh -R 2000:localhost:22 somewhere.else
SSH_PORT=2000 darcs get localhost:some/repo
But this requires the user to have a ssh server on their local
machine, and ssh would prompt the password and maybe use the wrong
username to connect back to
Petr Rockai wrote:
trentb...@gmail.com (Trent W. Buck) writes:
I suppose I could modify it trivially to (untested)
busybox httpd -f -p 12345 -h .
ssh -R 12345:127.0.0.1:12345 fs darcs get --complete
http://127.0.0.1:12345 x
kill $!
...which wouldn't require putting a key
Dan Pascu d...@ag-projects.com writes:
I always have to make a clone of a repo before doing any pull, because
if there is a conflict, the repo will be completely messed after the
pull. Working with the constant fear that a simple pull can result in
a big mess that could take a lot of time and
Dan Pascu d...@ag-projects.com writes:
[issue1187] Darcs simply provides an empty file for one of the
versions to the external merge tool
IIRC that happens when there's a mv; darcs diff and external merge don't
handle that case. I don't have an external merge tool available right
now, so I
Eric Kow ko...@darcs.net writes:
If I understand correctly, you're trying different ssh commands (plink
-P, ssh -p, etc) in succession and returning the first one which
succeeds.
FWIW, I normally don't supply options on the CLI; instead, they go in
.ssh/config, e.g.
Host *.example.net
Eric Kow ko...@darcs.net writes:
I don't really remember the issues behind it, but I seem to remember
that all the Darcs/Windows guides that get written talk about setting
a key with an empty passphrase. I think it may be something to do
with PuTTY grabbing the passphrase from stdin instead
Max Battcher m...@worldmaker.net writes:
So any good Darcs on Windows guide will have to explain SSH keys and
agents (pageant), because PuTTY's agent doesn't do some of the
auto-launch, auto-cookie magic that OpenSSH does (particularly with
the (awesome) super-agents that modern distros
Matthias Kilian k...@outback.escape.de writes:
On Fri, May 28, 2010 at 09:50:22PM +0100, Eric Kow wrote:
What if the user renames their plink to ssh?
Even worse: what if someone with a non-Windows operating system has
some command named `plink' installed in his PATH, where that `plink'
does
Isaac Dupree m...@isaac.cedarswampstudios.org writes:
(Is there anyway to create a repo with no patches in it that has the
same patch-format, i.e. darcs1 vs. darcs2, as another one? I didn't
see any options in either `darcs get` or `darcs init` that would let
me do this. It's needed so that
Eric Kow ko...@darcs.net writes:
So how does this deps.pl work? Is it doing something which effectively
works out the same as computing a minimal context? Is it reasonable to
expect the idea to work (not to speak of the implementation?).
Last time I looked, it worked by creating an empty
Eric Kow ko...@darcs.net writes:
Alternatively, you can download the tarball from
http://darcs.net/releases/darcs-2.4.4_1.tar.gz and build it by hand as
explained in the README file.
Due to a cock-up on my part, Debian's darcs 2.4.4-1 has the _1 fix in
the orig.tar.gz, but patches it back to
Eric Kow ko...@darcs.net writes:
Salvatore and others,
http://darcs.net/releases/darcs-2.4.4.tar.gz
You have one week. :-)
Works for me. I'll upload to sid when it hits hackage.
___
darcs-users mailing list
darcs-users@darcs.net
Salvatore Insalaco kirb...@gmail.com writes:
Hi guys,
I know that this may be unpopular, but now that we have official
packages (on Windows and soon on OS X) I propose this change on the
release policy:
Make the final (no RC, the final tar.gz) release of darcs available
to packagers one
Max Battcher m...@worldmaker.net writes:
So this is a fun bundle of patches..∙ After the get it done but try
not to touch/break anything important first attempt at Graphing, this
bundle of patches factors out the common parts of tabulateRepo/graphRepo.
Stupid question: are these histographs,
Simon Michael si...@joyful.com writes:
- -backward-compatible is long, so awkward for ui and docs and
conversation. It's also easy to misremember as backwards. -bc is
shorter but less clear.
It's also not clear how far the backwards compatibility extends :-)
As Devil's advocate, let me suggest an alternate repo format naming
strategy: simply a monotonically-increasing natural number, ordered by
implementation date.
Thus, --old-fashioned-inventory would be --format=1.
Thus, --hashed would be --format=2.
Thus, --darcs-2 would be --format=3.
darcs init
Zooko Wilcox-O'Hearn zoo...@gmail.com writes:
Oh by the way there is a ticket to backport darcs-2 to Hardy:
https://bugs.launchpad.net/hardy-backports/+bug/410905
It is blocked on getting someone to testing the following tools which
are already in hardy and which depend on darcs and which
Max Battcher m...@worldmaker.net writes:
I know that there are issues already in the tracker for this, but I
had a quick noodle of an idea (tangentially borrowed from a git
discussion) and wasn't sure which one might be best to attach to, or
if I should just post as a new one.
Here's the
Trent W. Buck trentb...@gmail.com added the comment:
Thanks for extending these tests, Dmitry.
Dmitry Astapov wrote:
-darcs init --repo R S # Create our test repos.
+mkdir -p R S# Create our test repos.
+(cd R; darcs init)
+(cd S; darcs init)
Mea culpa
Guillaume Hoffmann guilla...@gmail.com writes:
I also have it, yet linking fails.
I can reproduce this on Debian Sid, with a local build of hashed-storage
0.4.10 (everything else is stock Sid packages):
# runghc Setup configure -fstatic
[...]
# runghc Setup build
[...]
[139
Trent W. Buck trentb...@gmail.com added the comment:
Eric Kow wrote:
Hi Trent, may I ping you on this? It seems to be blocking patch136
Sorry about the huge delay. I went to apply this to HEAD, and I got
this:
darcs: bug in get_extra commuting patches:
First patch is:
Wed Aug 12
New submission from Trent W. Buck trentb...@gmail.com:
1 patch for repository http://darcs.net:
Fri Mar 26 22:12:40 EST 2010 Trent W. Buck trentb...@gmail.com
* Extend issue1646 with additional pathologies.
--
files: extend-issue1646-with-additional-pathologies_.dpatch, unnamed
Trent W. Buck wrote:
+ln -s /dev/null l
That should've been /dev/zero, but right now it doesn't matter much,
as AFAICT links to devices are treated as empty regular files.
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org
Max Battcher m...@worldmaker.net writes:
[...] and I'm sure it takes plenty of learned knowledge from RFC822's
experience...
Without seeing some evidence (i.e. a whitepaper), I would not want to
make that assumption. Plenty of weenies NIH some new format or language
precisely because they
Jason Dagit dag...@gmail.com writes:
[...] I've heard that sqlite has a much better track record in this
regard. I don't know enough about hashed-storage to say whether it
could be used to store the inventory/patch metadata.
The sqlite people claim (claimed?) that it's too dangerous to use
Max Battcher m...@worldmaker.net writes:
For YAML there are predominantly two standard parsers available in
most languages: a language-specific parser and a binding around
libsyck, the C SAX-like parser.
According to Wikipedia,
- YAML 1.2 is the latest specification.
- yaml-cpp (C++)
Trent W. Buck trentb...@gmail.com added the comment:
Eric Kow wrote:
Can this go in, Trent?
It works for me with GHC 6.12 and Cabal 1.8, but someone needs to test
this with whatever other versions we claim to support.
Also note I only tested the first patch in this bundle.
https
Eric Kow ko...@darcs.net writes:
New defaults for Darcs 2.5
--
* pull/push/send --no-set-default
- ... but add an online reminder whenever you interact with a
non-default repo about how to set the default
* send --edit-description
* record --no-test
*
Max Battcher m...@worldmaker.net writes:
[...] Of course, RFC822 is full of loopholes and surprisingly hard to
parse in reality [...] I think I have a reasonable suggestion that is
easier to parse than RFC822, but carries a similar effect: YAML
formatted darcs comments.
Can you support this
Petr Rockai wrote:
t...@cybersource.com.au (Trent W. Buck) writes:
Max Battcher m...@worldmaker.net writes:
[...] Of course, RFC822 is full of loopholes and surprisingly hard
to parse in reality [...] I think I have a reasonable suggestion
that is easier to parse than RFC822, but carries
Trent W. Buck trentb...@gmail.com added the comment:
This (should) resolve issue1508 -- testing now.
--
nosy: +twb
__
Darcs bug tracker b...@darcs.net
http://bugs.darcs.net/patch184
Matthias Kilian k...@outback.escape.de writes:
On Wed, Mar 17, 2010 at 07:24:36PM +0200, Yitzchak Gale wrote:
...under what circumstances would Debian stable users need to
*compile* (as opposed to fetching a binary) *new* versions of Darcs?
For the new bit, I think it would be if we were ever
Eric Kow ko...@darcs.net writes:
On Tue, Mar 16, 2010 at 22:45:32 +, Ganesh Sittampalam wrote:
After just going through a bit of pain with having to constrain
dependent packages to old versions for GHC 6.8.3, I found myself
wondering how long more we're going to support GHC 6.8 for. Do we
Trent W. Buck trentb...@gmail.com added the comment:
Alexey Levan b...@darcs.net writes:
New submission from Alexey Levan exle...@gmail.com:
Mon Mar 8 06:41:07 EET 2010 exle...@gmail.com
* Resolve issue 1397: distinguish between no arguments and no valid
arguments cases in darcs
Niall Murphy nmur...@gmail.com writes:
What about doing it in the other direction, that is, giving the
responsibility of inserting the revision numbers into your documents
to the build process, instead of darcs ?
The idea would be to use a Makefile that inserts in all your .tex
documents, a
Jason Dagit da...@codersbase.com writes:
On Wed, Mar 10, 2010 at 3:22 AM, Eric Kow ko...@darcs.net wrote:
That may be a bit too subtle. Maybe plain English will work.
$ darcs status
(This is an alias for darcs whatsnew -sl)
M ./corpus-building/flatten-inputs.hs -1 +1
R ./harness/Makefile
Trent W. Buck trentb...@gmail.com added the comment:
This looks like a bug report, not a patch.
Bug reports should be sent to b...@darcs.net.
--
nosy: +twb
__
Darcs bug tracker b...@darcs.net
http://bugs.darcs.net/patch174
Max Battcher m...@worldmaker.net writes:
http://blog.worldmaker.net/2010/mar/03/storing-documents-version-control-musdex/
[...] Basically, in darcs terms: its a prehook/posthook duo that
pre-record extracts the contents of given zip archives (which may be
.docx, or .odt files for instance)
Guillaume Hoffmann guilla...@gmail.com writes:
False alert, I could build a static binary with cabal install -f-curl
-fstatic.
This is ultimately Kerberos' fault. See http://bugs.darcs.net/issue806.
The workaround you found (above) is the only one I know works, though I
suppose you could try
Jason Dagit da...@codersbase.com writes:
Current we have darcs 2.4 beta 3 which is the same source code as
2.3.99 (or something close to that). What I find confusing is that
one version of darcs has several aliases. From my perspective, we
will continue to have confusing version numbering
New submission from Trent W. Buck trentb...@gmail.com:
1 patch for repository http://darcs.net/releases/branch-2.4:
Fri Feb 19 11:34:37 EST 2010 Trent W. Buck trentb...@gmail.com
* Print an intelligible error on darcs dist for this project.
Before:
$ darcs dist
autoconf: error
New submission from Trent W. Buck trentb...@gmail.com:
1 patch for repository http://darcs.net/releases/branch-2.4:
Fri Feb 19 11:39:43 EST 2010 Trent W. Buck trentb...@gmail.com
* Remove intermediary files from cabal sdist tarball.
AFAICT these files are generated during make html pdf
Mark Stosberg m...@summersault.com writes:
Here's my use case: I'm doing a peer review of a set patches that relate to a
certain ticket number. I want to make sure that I review each changed file,
so I would use this report as a checklist.
In the past I've accomplished this by using darcs
Isaac Dupree m...@isaac.cedarswampstudios.org writes:
Petr Rockai wrote:
Ganesh Sittampalam gan...@earth.li writes:
(It's quite likely there's something I don't understand about darcs, since
sometime I used 'darcs send' and it put some old draft patches of mine that
weren't in the current
Petr Rockai m...@mornfall.net writes:
Ganesh Sittampalam b...@darcs.net writes:
This breaks the build for me with GHC 6.12.1, cabal-install 0.8.0, Cabal
1.8.0.2. Haven't investigated further yet:
Setup.lhs:225:43: Not in scope: `packageDeps'
cabal: Error: some packages failed to install:
Petr Rockai wrote:
t...@cybersource.com.au (Trent W. Buck) writes:
This is a known problem. I can't remember where it is in the BTS, but
we were talking about it on #darcs. Here's the minimal test: [...]
I'm using hashed-storage-0.4.4 and Darcs 2.3.1 (+ 426 patches).
Are you sure?
I
Jason Dagit da...@codersbase.com writes:
bindisttest/a/b
index:
working: 5847c8b50a3191775d91cbaf8029fd1a75725517b0c70dde5bff759fc67ec1f8
This is a known problem. I can't remember where it is in the BTS, but
we were
Trent W. Buck trentb...@gmail.com added the comment:
Sorry about the review delay.
Daniel Dickison wrote:
Mon Jan 11 16:03:34 EST 2010 Daniel Dickison danieldicki...@gmail.com
* Accept issue1726: Files with _darcs prefix are always boring
+# Passing --boring should definitely succeed
Daniel Dickison b...@darcs.net writes:
Unless I wrote it incorrectly, the regression test in patch135 already
checks to make sure _darcs/foo gets skipped:
+not darcs add -r _darcs
+not darcs add -r --boring _darcs
+
+# ...as well as user-created files under _darcs (?)
+touch _darcs/foo
Petr Ročkai b...@darcs.net writes:
Daniel Dickison b...@darcs.net writes:
If you wouldn't mind a possibly naïve question, why is it necessary to
special case the _darcs directory when the default boring file already
contains the following line? (^|/)_darcs($|/)
I assume this is because the
Petr Ročkai b...@darcs.net writes:
If someone managed to create patches referring to files under _darcs
(by removing that _darcs entry from their boring file), I can only
assume that BAD THINGS would happen.
Out of curiosity, I simulated such an attack:
$ with-temp-dir
with-temp-dir:
Thomas Hartman b...@darcs.net writes:
Thomas Hartman thomashartm...@googlemail.com added the comment:
What and where are the CLONE_FS (...) flags ?
...darcs.net $ find -type d -name _darcs -prune -o -name *.hs -print |
xargs -i grep CLONE {} # (no output)
FYI, with GNU grep this is
Trent W. Buck trentb...@gmail.com added the comment:
Daniel Dickison wrote:
On Jan 13, 2010, at 9:59 PM, Trent W. Buck wrote:
I'm concerned that using _darcsfoo both times might trip unrelated
bugs in pending. I suggest using _darcsbar the second time, and
simply doing a normal record
Sittampalam, Ganesh ganesh.sittampa...@credit-suisse.com writes:
Trent W. Buck wrote:
Reinier Lamers tux_roc...@reinier.de writes:
Op woensdag 23 december 2009 12:00 schreef je:
Have you already applied this? I may have found a bug on it.
I considered applying it tonight, but it raised
Reinier Lamers tux_roc...@reinier.de writes:
Op woensdag 23 december 2009 12:00 schreef je:
Have you already applied this? I may have found a bug on it.
I considered applying it tonight, but it raised some more questions on IRC:
[21:26] Heffalump it effectively throws away the existing
Isaac Dupree m...@isaac.cedarswampstudios.org writes:
Trent W. Buck wrote:
Reinier Lamers tux_roc...@reinier.de writes:
Op woensdag 23 december 2009 12:00 schreef je:
Have you already applied this? I may have found a bug on it.
I considered applying it tonight, but it raised some more
Ivan Lazar Miljenovic ivan.miljeno...@gmail.com writes:
I consider it show-stopping in the sense that I keep having people
on #gentoo-haskell asking me why they can't compile darcs 2.3.1
because that error comes up, and I have to explain to either disable
documentation or downgrade Cabal (if
Alberto Bertogli albert...@blitiri.com.ar writes:
But the main reason was that with git, I create a branch in 0.007s,
using one command. With darcs, I have to cd out of the repository, do
a get, and then cd back (either to the original or to the new one).
FWIW, what I usually type is darcs
Petr Rockai m...@mornfall.net writes:
Nathan Gray kolib...@graystudios.org writes:
How exactly do you make one of the repo tarballs? I would like
darcs get /path/to/repo _tmp
cd _tmp
tar cvzf ../repo.tgz .
Wouldn't it be more efficient[0] to only archive _darcs, and do a darcs
revert --all
Reinier Lamers tux_roc...@reinier.de writes:
* Investigate how to handle the ICU dependency on Windows; if we have
to, just bundle the ICU source.
From the Debian integrator to the release manager:
It will annoy me if the source tarball for 2.4 contains icu, because
I'll have to either
Johan Tibell johan.tib...@gmail.com writes:
$ time ssh fs darcs get --lazy $PWD $PWD+issue1234
[...]
$ du -sh $PWD $PWD+issue1234
52M /home/twb/Desktop/Darcs/darcs
4.7M/home/twb/Desktop/Darcs/darcs+issue1234
Is it best practice to create your topic branches
Eric Kow ko...@darcs.net writes:
But for larger projects, I tend to have a single directory just for that
project
darcs-hacking/unstable
darcs-hacking/kowey
darcs-hacking/review-291
(so cd darcs-hacking; darcs get --lazy http://darcs.net review-291)
It would probably be more efficient
Simon Marlow marlo...@gmail.com writes:
On 28/12/09 18:29, Eric Kow wrote:
I recommend just trying this to see how it feels. So I think what
makes --lazy work well in practice is that in practice, one does not
actually consult the patches that are far back in history very often.
If they
Johan Tibell johan.tib...@gmail.com writes:
My main worry (personally) is losing the simplicity of Darcs, which I
think is a quality that we should hang to very tenaciously.
Simplicity is a good principle, and I think it's one worth sticking
too. However, sometimes you need to do complicated
Thomas Hartman thomashartm...@googlemail.com writes:
In general, even without bringing the need for an API in, it seems
like currentDirectory agnosticism is a better way to go.
+1.
___
darcs-users mailing list
darcs-users@darcs.net
Petr Rockai wrote:
From looking at the patch, the PNG logos seem to have changed for
whatever reason. Have you maybe included too many files in the automated
whitespace cleanup process?
Oops, that's undoubtedly a screw-up. The last bundle only affected
.lhs and .hs files, but this time I
Reinier Lamers tux_roc...@reinier.de writes:
- interactive patch editing
I'm not sure we ever really finished the design of the user
interface. We probably should before 2.4...
We tried discussing this a number of times. I haven't tried this
feature out yet. It's really something we should
What are these getLog messages?
$ darcs --version
2.3.1 (+ 416 patches)
$ find [^_]*/ -depth -type d -exec \
darcs record --no-test -am Whitespace cleanup in {}. {} \;
[...]
Recording changes in src/Darcs/Witnesses:
Patch name as received from getLog:
Jason Dagit da...@codersbase.com writes:
Unfortunately, my computer locked up during my first pass through the
benchmarks so I don't have the exact commands handy. The above is
from and I think it should be close.
It might be worth playing with the ulimit shell builtin, to restrict
e.g. the
Eric Kow ko...@darcs.net writes:
he [wants] make-me-a-branch command [to be] near instantaneousness.
Doing the operation on the fileserver (instead of over NFS), branching
is fast enough for me. With the Darcs repository:
$ time ssh fs darcs get --lazy $PWD $PWD+issue1234
Copying
Stephen J. Turnbull wrote:
* Incrementally building up the next commit using a staging area.
For haskell libraries, --builddir /var/tmp/staging ?
That's not what he means. He's talking about using the index, eg.
$ gnuclient a.h a.c # change prototype and implementation of foo
$ git
Thomas Hartman thomashartm...@googlemail.com writes:
it would be useful for patch-tag to turn off hard linking for darcs
storage (in pristine.hashed, patches, and so on). can anyone suggest
the most straightforward way to do that?
Why would it be useful?
A straightforward way would be to
Marnix Klooster marnix.kloos...@gmail.com writes:
On 11-12-09 03:44, Trent W. Buck wrote:
Dave Love b...@darcs.net writes:
The Emacs maintainers rejected the Darcs support (despite supporting
the other major free VCSs) :-(.
I guess you mean that the GNU Emacs maintainers are unwilling
Marc Weber marco-owe...@gmx.de writes:
- each git commit has a uniq name: its hash.
Does darcs use hashes as well now?
It has had hashes since 2.0.0.
Can I say darcs unpull $HASH ?
Or darcs pull $HASH $REMOTE_REPO ?
Yes, using --match. See darcs help patterns.
In darcs you can
Marc Weber marco-owe...@gmx.de writes:
Yes, I know about the --hashed option etc.
If --hashed is still meaningful for you, consider converting your
project to the darcs-2 format, which should be better than the iterim
hashed format.
But when running darcs changes -v | less
I can't see them.
dons Grumpy Old Man hat
Dave Love b...@darcs.net writes:
Wed Dec 9 23:22:06 GMT 2009 Dave Love f...@gnu.org
* Contribute vc-darcs.el for Emacs VC support.
As Jason noted, this would be appropriate for contrib/.
The Emacs maintainers rejected the Darcs support (despite supporting
Trent W. Buck trentb...@gmail.com added the comment:
Eric Kow wrote:
On Wed, Dec 09, 2009 at 05:34:54 +, Trent W. Buck wrote:
Creating patch to http://darcs.net/darcs-bugtracker;...
Is it a really good idea to cc patches for non darcs-specific stuff
to the tracker?
I don't know
New submission from Trent W. Buck trentb...@gmail.com:
Creating patch to http://darcs.net/darcs-bugtracker;...
Wed Dec 9 16:29:32 EST 2009 Trent W. Buck trentb...@gmail.com
* Use relative path for logfile.
This shouldn't affect the production instance, but will make it easier
Ganesh Sittampalam b...@darcs.net writes:
This seems to already have been applied.
That was me. I was expecting darcswatch to close the patch for me; I
guess patch34 predates that darcswatch-fu.
___
darcs-users mailing list
darcs-users@darcs.net
Trent W. Buck trentb...@gmail.com added the comment:
Ganesh Sittampalam wrote:
This looks sane to me - Trent, could you just confirm?
Sorry; I meant to look at this when it first came in.
The old code used to call src/preproc with/without --html.
That argument got lost when Petr moved
Ganesh Sittampalam b...@darcs.net writes:
I guess you've tested it on at least the darcs repo's .authorspellings
file - any others?
If someone collects pathological .authorspellings examples, I suggest
turning them into a tests/foo.sh script.
___
[documentation manager hat on]
Mark Stosberg m...@summersault.com writes:
I've accumulated several darcs tips I'd like to share, but I'm not
sure where the best place to put them is. The manual? The wiki? A
series of blog posts?
First: anywhere is better than nowhere. Even if I don't like
Mark Stosberg m...@summersault.com writes:
I'm having trouble installing cabal-install 0.6.2 on a new laptop
today, on Karmic Koala.
cabal-install is available in Lucid[0]. You might be able to simply
backport that version, since the ghc6 versions in karmic and lucid are
identical. The
Henrik Hjelte hen...@evahjelte.com writes:
On Thu, Dec 3, 2009 at 3:54 AM, Trent W. Buck t...@cybersource.com.au wrote:
Henrik Hjelte hen...@evahjelte.com writes:
The absence of symlink-support makes it impossible to migrate a lot of
repositories to darcs from other revision control systems
Jason Dagit da...@codersbase.com writes:
Okay, maybe general push permission shouldn't be allowed, but I was
hoping I'm trusted enough in the darcs community that I could be given
permissions.
I have no problem with giving Jason push access to the wiki repo.
Henrik Hjelte hen...@evahjelte.com writes:
The absence of symlink-support makes it impossible to migrate a lot of
repositories to darcs from other revision control systems. Adding a
script that manages symlinks (like update-symlinks.sh) script is not a
solution for that.
Why isn't it a
Joachim Breitner m...@joachim-breitner.de writes:
the problem is that roundup does not distinguish between hand-written
comments and automated messages. You want the former on -users (and
that is why users is subscribed to roundup), but not the latter. If
someone wants to implement the
Sergei Trofimovich b...@darcs.net writes:
Sun Nov 22 00:50:06 EET 2009 Sergei Trofimovich sly...@inbox.ru
* bump array, containers, unix constraints in .cabal (ghc-6.12rc1)
Pathch does not fully fix -HEAD, but it's enought to make -stable
2.3.1 work on 6.12rc1. Worth hitting stable.
Stephen J. Turnbull step...@xemacs.org writes:
Darcswatch should be retargeted to -devel.
+1.
I thought it'd be useful to avoid accidentally re-reviewing bundles, but
it's far more likely that I'll ignore a given bundle than re-review it.
In the former case, the darcswatch post means a second
I wanted to test my Debianization of Darcs against the latest checkout.
This requires an upstream source tarball (like you see on hackage).
I couldn't work out how to make the tarball. I tried:
$ darcs dist
autoconf: error: no input file
Dist aborted due to predist failure
$
Jason Dagit da...@codersbase.com writes:
On Sun, Nov 22, 2009 at 10:21 PM, Trent W. Buck
t...@cybersource.com.auwrote:
I wanted to test my Debianization of Darcs against the latest checkout.
This requires an upstream source tarball (like you see on hackage).
I couldn't work out how to make
Reinier Lamers tux_roc...@reinier.de writes:
* We depend on a new version of haskeline, that depends on a new version of
utf8-string
* We specify a utf8-string dependency in darcs.cabal, only to make sure
the version haskeline uses is recent enough.
The second option feels dirty,
Ganesh Sittampalam wrote:
On Thu, 12 Nov 2009, Trent W. Buck wrote:
Florent Becker florent.bec...@ens-lyon.org writes:
The object of these patches is to add a --dont-frobnicate option for each
--frobnicate option. That way, you can put command frobnicate in your
prefs file, and still use
Ganesh Sittampalam gan...@earth.li writes:
On Tue, 17 Nov 2009, Trent W. Buck wrote:
Ganesh Sittampalam gan...@earth.li writes:
Generally when reviewing patches, I read them directly, perhaps have a
look at the source they apply to, and then decide that they're fine so
long as the tests
Sittampalam, Ganesh ganesh.sittampa...@credit-suisse.com writes:
Trent W. Buck wrote:
Ganesh Sittampalam gan...@earth.li writes:
On Tue, 17 Nov 2009, Trent W. Buck wrote:
[...] patches that don't apply cleanly are automatically set to
needs-amend?
I think the difficulty here is uniquely
Ganesh Sittampalam gan...@earth.li writes:
Generally when reviewing patches, I read them directly, perhaps have a
look at the source they apply to, and then decide that they're fine so
long as the tests pass. Actually keeping track of them between that
point and running the tests and pushing
Jason Dagit wrote:
I suppose there are security issues to consider.
Certainly DOSing would be trivial in the naïve implementation :-)
___
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
Florent Becker florent.bec...@ens-lyon.org writes:
Not in every case. It is the case when using darcs diff, but not when
using darcs whatsnew, and also annotate as a patch viewer. But maybe
it could be always on when using these commands?
Oops, I had forgotten about whatsnew --unified.
*I*
1 - 100 of 1201 matches
Mail list logo
