Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2014-01-08

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

All times shown according to UTC.

Time Nick Message
00:57 gh_ joined #darcs
04:35 preflex joined #darcs
06:47 lelit joined #darcs
07:18 raichoo joined #darcs
07:36 MasseR sm: Hmm... no. Were you able to see it working on my instance?
07:37 MasseR Can you check with futon that the view is working?
08:13 amgarchIn9 joined #darcs
10:11 dcoutts joined #darcs
10:15 amgarchIn9 joined #darcs
10:24 devdos joined #darcs
10:26 devdos joined #darcs
10:28 augulus joined #darcs
10:43 amgarching joined #darcs
11:13 amgarching joined #darcs
11:46 f-a joined #darcs
12:59 f-a joined #darcs
14:15 amgarching joined #darcs
14:43 preflex joined #darcs
14:45 amgarching joined #darcs
15:05 owst joined #darcs
15:08 sm MasseR: hi, can you make a private repo with "simon" a member at http://peitto.info/MasseR  ?
15:10 MasseR sm: You should see both foobar and barfoo
15:10 MasseR I can see them both with MasseR2
15:11 sm yes I do. hmm
15:13 sm in hub.darcs.net's futon, in the view_by_private_member view, there is a record with owner "simon", name "test" (my test repo) and members including "MasseR"
15:14 sm oh, ie my test repo is present in the view. Shouldn't that be enougnh ?
15:14 sm for you to see it ?
15:36 sm (MasseR)
15:37 f-a joined #darcs
15:44 mizu_no_oto joined #darcs
16:16 raichoo joined #darcs
16:41 gh_ joined #darcs
18:22 mizu_no_oto joined #darcs
18:43 amgarching joined #darcs
19:31 gh_ hi
19:31 gh_ I've just sent a patch for `darcs log --fast-export` if anyone want to try. I'm not screening it. http://bugs.darcs.net/patch1111
19:50 mornfall Haha, you got to be kidding me.
20:13 gh_ mornfall, some context in case you missed it: http://lists.osuosl.org/pipermail/darcs-users/2013-December/026978.html
20:18 mornfall I just find it funny that it was a big nonono back in 2010.
20:20 mornfall http://bugs.darcs.net/patch332
20:23 sm gh_, mornfall ++
20:23 sm let's round up those early objectors and..
20:24 sm ...send them to the coding mines!
20:24 sm I'll give that a try gh
20:24 sm is there some easy way I can pull it ? eg on darcs hub ?
20:26 sm is this one similar in spirit to 332, just updated ?
20:26 gh_ mornfall, I'm sorry about that… back then, if I had had more confidence to give my opinion, I would have backed your choices. also, I don't remember that bundle :x
20:29 gh_ sm, similar to 332 no. I just made the Export part of darcs-fastconvert compile with current darcs, then copy it to Darcs.UI.Commands.Log
20:30 mornfall gh_: don't worry, not your fault
20:30 mornfall also this was one of the less catastrophic conflicts I had with the rest of the team...
20:35 sm gh_: so.. where can I pull from ?
20:37 gh_ sm, sorry! apply http://bugs.darcs.net/patch1111 to the latest screened branch
20:37 sm but it's 2014 and I don't want to mess with file attachments :)
20:37 sm can you push your branch to your hub account ?
20:37 gh_ darcs apply -i http://bugs.darcs.net/file4563/implement-log-__fast_export-to-output-git_fast_import-stream.dpatch
20:38 sm that way we could easily read the code together, also
20:38 gh_ okay, allow me a couple minutes
20:38 sm aha, thanks
20:39 sm ah, that way doesn't bring in dependencies
20:39 sm "remove useless check of xml-output in get and convert", in this case
20:40 gh_ pull it from darcs.net
20:40 sm oh, it's in screened ?
20:40 gh_ yes, since today
20:40 sm great, thanks
20:40 gh_ (I'm getting errors while forking darcs-screened on hub.darcs.net)
20:40 sm oh xml patch is. got it
20:40 gh_ oh, it worked at the 3rd attempt
20:41 gh_ sm, done http://hub.darcs.net/gh/darcs-screened_1
20:42 sm gh_: sorry. This might have been more reliable: ssh hub.darcs.net init darcs-screened-export 'export branch'; darcs push -a hub.darcs.net:darcs-screened-export
20:43 gh_ sm, yes but way slower
20:44 sm I see.. yeah
20:45 sm gh_: hub's error logs aren't very clear.. did see something like "Couldn't fetch `0000000457-0d0636040fa5f0f1e8cddcf4fe279eb46ec69133af026bae63a3cacadd5cdca2'" ?
20:45 sm did you
20:46 gh_ something like this yes, with a list of cache paths
20:47 sm I guess it was intermittent
20:47 sm I've been seeing this kind of error doing command-line darcs gets as well
20:47 sm in recent times
20:48 sm I wonder if it's because of clearing darcs' patch cache
20:49 MasseR sm: Sorry, left work right  after I last answered you. As long as there is the key (owner, member) with the document as value it should work (it could be other way around too)
20:53 sm MasseR: no problem. https://gist.github.com/simonmichael/8324429 is what I have installed as the view code, does it look right ?
20:54 MasseR Hmm... Quickly checking there might be an issue there
20:55 MasseR sm: Check the gitst comment
20:56 MasseR *gist
21:00 f-a joined #darcs
21:05 sm MasseR: I updated the view code in futon, removed and readded the members on my test repo, still no joy
21:06 sm let me stare at your schema code again
21:13 sm ah! forgot to also click save document in futon. That always gets me
21:13 sm MasseR: working for me.. and you can see my private test repo now, eh ?
21:14 MasseR Haha :D
21:14 MasseR Let me check
21:14 MasseR Yup
21:14 MasseR test - for testing
21:14 MasseR With a lock on it
21:14 sm finally! merged, thanks a lot
21:15 MasseR Btw does darcshub close issues if patch has certain tags?
21:15 sm yes
21:16 MasseR http://hub.darcs.net/simon/darcsden/issue/52 and should this be closed now?
21:16 sm let me document that. Yes please
21:42 sm MasseR: hub.darcs.net#can-i-reference-or-close-issues-with-a-commit
21:50 sm gh_: I did dist/build/darcs/darcs log --fast-export | (mkdir t && cd t && git init && git fast-import)
21:51 sm successfully exported darcs' 10k patches, and tags, in a minute or so
21:51 sm I think that's awesome
21:52 gh_ :-)
21:52 gh_ it has been awesome since 2010, we just did not know it
21:52 sm *I* knew it
21:53 sm but didn't do it :)
21:53 gh_ yes, that's also what I wanted to say
21:53 sm well, why would I, mornfall already did it
21:54 sm I don't remember/understand why there was resistance to this, all other modern vcs's include import/export
21:54 sm only a dead-end project would not have it
21:58 sm how would you feel about moving it to the "export" command ?
21:58 sm since it doesn't play with log's options, and that's how other vcses do it
22:01 gh_ yeah, looking at patch332 I'm inclined to think that convert --export (or directly export as you say) is a better choice
22:02 gh_ also, export needs to replay the repository, so it's not really a "fancy log option" as I said on the mailing list. from the implementation point of view.
22:10 mizu_no_oto joined #darcs
22:20 computionist joined #darcs
22:21 * sm enjoys another git WTF moment
22:21 sm you've just gotta roll with it
22:34 raichoo joined #darcs
22:37 raichoo joined #darcs
23:12 lelit joined #darcs

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