| Time |
S |
Nick |
Message |
| 00:00 |
|
lispy |
SyntaxNinja: hey |
| 00:00 |
|
lispy |
SyntaxNinja: how are things? |
| 00:01 |
|
SyntaxNinja |
hiya lisp |
| 00:01 |
|
SyntaxNinja |
pretty good, you? |
| 00:03 |
|
lispy |
um...don't ask :) |
| 00:03 |
|
lispy |
is in the middle of a move that was spurred by a non-mutual break-up |
| 00:03 |
|
lispy |
but, things have been worse in the past, so considering i'm not doing too bad |
| 00:04 |
|
lispy |
SyntaxNinja: is there anything that prevents darcs from being buildable with cabal? |
| 00:07 |
|
SyntaxNinja |
lispy: sucks, man. |
| 00:08 |
|
SyntaxNinja |
um, I don't think so particularly. I have built a darcs library with cabal in the past, but I never sent anyone the patch (bad ninja) |
| 00:09 |
|
lispy |
SyntaxNinja: ah, i was just thinking it wouldn't hurt anything have darcs buildable by cabal and might encourage certain things |
| 00:09 |
|
lispy |
SyntaxNinja: you should submit your patch :) |
| 00:10 |
|
SyntaxNinja |
yeah |
| 00:10 |
|
lispy |
SyntaxNinja: now that i'm moving and school is kinda shakey i found myself staring at the galois website again :) |
| 00:10 |
|
lispy |
bbiab, i have some more things to move |
| 04:39 |
|
twb |
Whee! |
| 04:39 |
|
twb |
Impossible case at Pull.lhs:194 compiled 03:40:25 Apr 16 2006 |
| 04:40 |
|
twb |
When calling "darcs pull" without an upstream repo in _darcs/prefs, AFAICT. |
| 05:14 |
|
Jerub |
I'd really like a hand hand-fixing a repo |
| 05:14 |
|
Jerub |
I have no idea how to go about it. |
| 05:14 |
|
twb |
Jerub: do tell. |
| 05:15 |
|
Jerub |
twb: this repo I have here: http://www.netrek.org/repos/netrek-client-cow/ |
| 05:15 |
|
twb |
Yeah? |
| 05:16 |
|
Jerub |
I pulled it accross from cvs using tailor, and it breaks applying the second patch |
| 05:16 |
|
twb |
What version of tailor? |
| 05:16 |
|
Jerub |
becuase the first 'patches' are all the same import into cvs, which are all the same import into darcs, but a second apart. |
| 05:16 |
|
Jerub |
latest from the main tailor repo |
| 05:17 |
|
twb |
I think that's a bit beyond my expertise. |
| 05:17 |
|
twb |
I'm still rather too dumb to use tailor. |
| 05:17 |
|
Jerub |
I think I could fix it by hand-editing darcs patches, but I'm too scared. |
| 15:49 |
|
|Lupin| |
Hello, darcs world. |
| 15:50 |
|
|Lupin| |
I just pulledsome patches And darcs reportsConflicts in two files. How can I see where they are, please ? |
| 15:50 |
|
|Lupin| |
I looked for "<<" but foun nothing. |
| 15:50 |
|
Igloo |
They're marked with v v v v and ^ ^ ^ ^ |
| 15:51 |
|
|Lupin| |
oh okthanks |
| 15:53 |
|
|Lupin| |
So what is beforeThe stars is what appears inthe patch andwhat is after the stars is the contentof the file, right ? |
| 17:07 |
|
tschwinge |
Hm. The documentation in the manual for `darcs changes --last=...' is not that extensive... |
| 17:09 |
|
tschwinge |
How can I easily gather the following information: |
| 17:09 |
|
tschwinge |
XML output for only the last change _of a specific file_? |
| 17:15 |
|
Xentac |
tschwinge: don't you want darcs changes --xml-ouput <file> ? |
| 17:15 |
|
lelit |
uhm, I don't think it's possible: --last works on the whole set of patches, not on those selected by other means |
| 17:16 |
|
tschwinge |
lelit: Exactly. |
| 17:16 |
|
Xentac |
oh, so you want the last blah patches for a single file |
| 17:16 |
|
tschwinge |
Yes. |
| 17:16 |
|
tschwinge |
Afk. |
| 17:18 |
|
lelit |
sorry, but what's the meaning of "afk"? |
| 17:21 |
|
idnar |
away from keyboard, usually |
| 17:21 |
|
lelit |
oh, couldn't figure out :) |
| 17:21 |
|
lelit |
thank you |
| 18:43 |
|
tschwinge |
I'm back. |
| 19:37 |
|
tschwinge |
So can anyone think of a way to get the `darcs changes --xml-output' of the last change to a specific file? |
| 19:38 |
|
C-Keen |
darcs changes --last=1 --xml ? |
| 19:38 |
|
C-Keen |
oh wait |
| 19:38 |
|
C-Keen |
reading the complete sentence helps |
| 19:40 |
|
tschwinge |
Indeed. ;-) |
| 19:40 |
|
tschwinge |
darcs is really not prepared to be used non-interactively. :-/ |
| 19:42 |
|
C-Keen |
tschwinge: still darcs changes --last=1 --xml file does it for me |
| 19:42 |
|
C-Keen |
hm |
| 19:42 |
|
C-Keen |
gaaa |
| 19:42 |
|
C-Keen |
I need sleep |
| 19:43 |
|
C-Keen |
sorry for the noise |
| 19:43 |
|
tschwinge |
C-Keen: Yep. That works. But only if the last change was done to the specific file. |
| 19:43 |
|
tschwinge |
... which probably is what you just noticed, I guess. ;-) |
| 19:43 |
|
C-Keen |
yes I noticed |
| 19:43 |
|
C-Keen |
:) |
| 19:44 |
|
C-Keen |
you are right darcs is not scriptable easily of course |
| 19:44 |
|
C-Keen |
I have been following the discussion on the mailing list |
| 19:45 |
|
tschwinge |
I'd like to improve that, but my Haskell foo is nonexistent. |
| 19:46 |
|
C-Keen |
same here |
| 19:46 |
|
C-Keen |
but I think it is nice to read |
| 19:47 |
|
tschwinge |
I'll now have a look at Juliusz's vc-darcs.el to see how he introduced Emacs to the wonders of darcs. |
| 19:48 |
|
tschwinge |
It sounds promising: |
| 19:48 |
|
tschwinge |
;; Internally, darcs identifies a patch by its hash, which you may |
| 19:48 |
|
tschwinge |
;; obtain by using changes --xml. We follow that approach in this |
| 19:48 |
|
tschwinge |
;; code. |
