Hmm, <br> <br> I just realized, I don't have e-mail setup on my linux box. hmmm. <br> <br> I just did a <br> <br> darcs send<br> <br> followed the instructions, and it seemed to go through okay. <br> <br> Anyone see it? It's named "cloakbombing"<br> <br> If not, I just edited my bounced e-mail and attached it as above. <br> <br> Jimmy<br><br><b><i>James Cameron <quozl@us.netrek.org></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> In addition to what Stephen said ... here's my comments.<br><br>On Tue, May 09, 2006 at 08:37:03AM -0700, Jimmy Huang wrote:<br>> Quick question:<br>> I imagine darcs record, then darcs send. <br>> Sends the whole tree. <br><br>Yeah, I thought that for about a minute, until I tested a darcs "get"<br>and found that darcs maintained a pristine copy. So the "record" and<br>"send" are diffs against this pristine copy kept locally. In a
manner<br>of speaking.<br><br>One trick to really learn this stuff quickly is to do a darcs "get" then<br>recursive copy the tree *twice* to some other place (/tmp), and then do<br>darcs operations between the two temporary copies, imagining that one is<br>yours and one is someone else's.<br><br>Things to remember are:<br><br>- that a "push" can operate over SSH or local filesystem, and that a<br> "send" is a "push" over e-mail.<br><br>- that a "get" is the initial "pull", and includes the effects of<br> "init",<br><br>- that a "pull" can operate over SSH, local filesystem, and HTTP,<br><br>- that an "apply" is the e-mail transport equivalent of "pull".<br><br>> Is there a way to do this only to a single directory<br>> like the robotd directory or a single file? <br><br>Yes. Had to do this myself last night, when my repository contained<br>unrecorded changes to several files but I wanted the changes to go as<br>separate patches. Just add the file names to the
"record".<br><br>-- <br>James Cameron mailto:quozl@us.netrek.org http://quozl.netrek.org/<br><br>_______________________________________________<br>netrek-dev mailing list<br>netrek-dev@us.netrek.org<br>http://mailman.us.netrek.org/listinfo/netrek-dev<br></blockquote><br>