Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2017-08-04

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:11 leg joined #darcs
01:52 ilbot3 joined #darcs
01:52 Topic for #darcs is now http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.12.5 is out http://darcs.net/Releases/2.12
02:18 Igloo joined #darcs
02:50 http_GK1wmSU joined #darcs
02:53 http_GK1wmSU left #darcs
03:55 Riastradh joined #darcs
05:55 ThomasLocke joined #darcs
06:45 lambdaGrp joined #darcs
06:46 lambdaGrp left #darcs
08:33 mal`` joined #darcs
11:19 jeltsch joined #darcs
13:23 gh_ joined #darcs
13:23 gh___ joined #darcs
13:36 gh___ Heffalump, ok one of these days I'll have a good look at the documentation. I hope to be patient enough to do something useful :D
16:38 jeltsch left #darcs
16:45 jeltsch joined #darcs
16:53 jeltsch left #darcs
17:01 gh__ joined #darcs
17:15 jeltsch joined #darcs
17:18 jeltsch left #darcs
17:19 jeltsch joined #darcs
17:23 Riastradh joined #darcs
17:24 Heffalump gh__: it might be a better use of time to accelerate the move to hub.darcs. I don't know.
17:27 gh___ joined #darcs
17:28 gh___ Heffalump, after looking at the configuration files on darcs.net I'm starting to feel the same .. :)
17:28 Riastradh joined #darcs
17:30 gh___ Heffalump, I'm not worried at all about migrating issues, more so about the patch submission process
17:31 gh___ sm, how can one notify some repo owner that one has patches for them?
17:31 gh___ on hub.darcs.net
17:32 sm gh___: there's no special mechanism, you have to notify them somehow to check their branches page
17:32 sm or, I believe you can attach a patch to an issue, if they have enabled an issue tracker
17:33 sm which should send email notification
17:33 gh___ sm, hmm
17:41 gh___ sm, is there any form of notification built in darcsden itself, that is, not by mail?
17:43 sm gh___: no
17:44 gh___ ok
17:44 sm other than the "flash" notices displayed at the top of the page, eg after you log in
17:45 gh___ Heffalump, is there some code lying around for implementing patch bundles submission, or was it just a project?
17:46 gh___ sm, maybe what is needed, instead of notifications, is an interface where patches or pull requests are first-class objects just like issues. I do not know how is the github interface for that.
17:54 sm maybe gh___
17:54 sm github PRs are like issues, as you say
18:21 Heffalump gh___: I believe there is code lying around, for both ends (darcsden to receive, darcs to send). I think darcs to send may already be built in.
18:22 Heffalump gh___: I thought you can upload a patch as a first-class thing, or you can attach it to an issue. I could be misremembering
18:23 Heffalump Despite good intentions, I haven't managed to spend much quality time on darcs stuff for quite a while.
18:52 gh___ Heffalump, from darcs' end, is it related to _darcs/prefs/post or is it something else ?
18:52 Heffalump gh___: umm. I think it is. There'd been functionality to do this in darcs for a very long time, but I can't remember if it needed tweaking at all and if so if that happened.
18:53 gh___ notdan_, ping ? :)
18:53 Heffalump https://hub.darcs.net/ganesh/darcsden-sendbundles may also be relevant
18:54 Heffalump I think it was BSRK aditya who implemented the patch sending/receiving stuff
18:55 gh___ *Darcs 2017: bring back our GSoC students*
18:55 gh___ oh yes, BSRK did also work on darcsden
18:56 gh___ http://darcs.net/GSoC/2013-Darcsden  http://darcs.net/GSoC/2015-Darcsden
19:00 gh___ there is nothing left of BSRK Aditya's blog or darcsden branch :/
19:03 Heffalump I think most of it was merged, except the bit about sending that I preserved
19:03 gh___ ok
19:24 jeltsch joined #darcs
19:25 gh___ Heffalump, the only patch in https://hub.darcs.net/ganesh/darcsden-sendbundles that is not in sm's darcsden repo is cdc21834e9efdcef512e9f9fd0f8903c16637f65 "Add ability to use send from client side to bundles feature"
19:36 gh___ ok I'm going to have a look at this patch
19:36 Heffalump makes sense, given it adds the endpoint for receiving it
19:37 Heffalump I remember that part of the issue with merging patches themselves was that sm was worried about spam, but I think that got overcome at some point
19:37 gh___ there have been +400 other patches after the time that particular patch was written (-_-;)
19:41 Heffalump yeah :-( that said, it looks like a fairly basic code addition, probably straightforward to port forward by copy+paste
19:41 gh___ yes
19:41 gh___ seems like the first step is to understand the logic of URL handlers
20:59 gh___ damn, building darcsden is long
21:00 gh___ also, mime-string (a dependency introduced by brsk aditya's patch) fails to build with ghc 8
21:26 gh___ building skylighting with ghc 8 is looong
21:44 gh___ ok done, the only blocking package is mime-string, I have just emailed Igloo in case he has a newer version of this package, if not the ambiguous occurrences of <$> seem easy to fix
21:51 Heffalump you can probably ask to take it over
21:53 gh___ looks like you guessed his answer right
21:56 Heffalump does he still ahve the darcs repo? :-)
21:56 gh___ no
21:57 gh___ so I'll have to use the code from the hackage package
21:58 gh___ or.. I could just inline in darcsden the functions from mime-string we need >:)
21:58 Heffalump :-)
22:08 gh___ ok another thing I have just seen is that darcsden does not build with current darcs head after ben's flags refactoring
22:08 gh___ nothing too complicated it seems
22:08 gh___ I've got to go, see you!
22:40 pointfree So "darcs changes --xml-output" works and will add feed items but "darcs apply --xml-output" does not (even with --dry-run). https://hub.darcs.net/pointfree/darcsden-feed-couchdb/browse/ssh-server/darcsden-ssh.hs#234
22:40 pointfree I'm not sure what the problem is.

| Channels | #darcs index | Today | | Search | Google Search | Plain-Text | summary