Perl 6 - the future is here, just unevenly distributed

IRC log for #darcs, 2016-01-21

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

All times shown according to UTC.

Time Nick Message
00:45 dino-_ I am using darcs 2.10.2 (release) and was just now trying to do a clone with --to-hash ..
00:45 dino-_ This appears to have no effect and I get all patches, is this just a bug?
00:46 dino-_ Or am I perhaps using it wrong? Here is my command: darcs clone --to-hash=052d68...(long hash here from log output) http://url...
00:48 dino-_ I can just --to-patch for now, that works
00:49 dino-_ just use^
00:50 vikraman joined #darcs
01:44 Big_G joined #darcs
02:27 drostie joined #darcs
02:46 mizu_no_oto joined #darcs
02:48 ilbot3 joined #darcs
02:48 Topic for #darcs is now Sprint in Seville, Spain 15-17th January | http://darcs.net/ | logs: http://irclog.perlgeek.de/darcs/ | darcs 2.10.0 is out http://darcs.net/Releases/2.10
03:41 dolio joined #darcs
04:43 drostie joined #darcs
06:41 peb` joined #darcs
07:06 Heffalump gh_: I'm fine with the machine readable thing btw
09:41 gh_ joined #darcs
10:25 gal_bolle joined #darcs
10:47 DarkFox joined #darcs
11:02 gh_ "darcs convert import" handles badly filepaths with spaces
11:07 gh_ ok since 2012 git fast-export puts quotes around paths that have spaces https://git.kaarsemaker.net/git/commit/ff59f6da840bb58058fef06721a2646daae50509/
12:01 mizu_no_oto joined #darcs
14:52 drostie joined #darcs
14:53 zack heya, I'm looking for information about how the darcs pull/push protocol works. Is that documented somewhere?
14:53 zack (other than in the code, that is :-))
15:13 Big_G joined #darcs
15:43 gh_ zack, hi, I'm afraid we don't have it documented yet
15:44 zack gh_: I see, no worries. Can you maybe point me to the relevant source code file(s)?
15:46 gh_ zack, yes, Darcs.UI.Commands.Pull and Darcs.UI.Commands.Push are the entry points of these commands
15:47 zack great, thanks a lot
15:47 gh_ zack, pull does actually two steps: fetch (which is also a hidden command) to generate a patch bundle, and then apply (see Darcs.UI.Commands.Apply) to apply it to the local repository
15:48 zack the main thing I'm curious about, given the fact that patches are reorderable, is how client/server tell each other which patches they have and which they lack
15:48 zack do they every time send to the other end the full list of patches?
15:50 Riastradh joined #darcs
15:52 gh_ zack, in case of pulling, the server does not need to do anything, it should just be available to read
15:53 gh_ zack, the function findCommonAndUncommon of the module Darcs.Patch.Depends does the job of comparing the histories of both repositories
15:54 gh_ zack, histories are actually called "inventories" in darcs' idiom, and they contain only patch metadata, so you don't download that much when you need to compare two repositories
15:54 zack ok, I see
15:55 gh_ zack, and the inventories are compared up to the last common tag. if there is no common tag then they are completely read indeed.
15:55 zack it looks like a smart set symmetric difference
15:55 zack ah, that's what I was missing: tags work as synchronization points
15:57 zack gh_: thanks, you've been really helpful
15:59 gh_ zack, you're welcome!
15:59 gh_ and, I should get going
16:10 xauth joined #darcs
17:03 zack left #darcs
18:35 Heffalump joined #darcs
21:31 Riastradh joined #darcs
21:56 drostie joined #darcs

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