Albert Reiner wrote:
Oh, I misunderstood.
Use `darcs record` to create the patch and make it part of your repo's
history. You can then use `darcs send` to send the patch - or several
at once - to someone. If you don't want darcs to mail the patch to
the recipient, you can use the --output option to specify a file.
Okay, I just tried it, and it works :-) Thanks!
I notice that I need to have read access to your repository to send you
a patch. I didn't expect that, but after thinking about it, I can see
that it makes sense. Let's see if I understand why:
We both start with patches A B. I make change C and you make change D.
So I have A B C and you have A B D. If I want to send you C, Darcs has
to merge the sets of changes C and D. This merger happens at the moment
of patch creation because that's when Darcs can be sure to have the two
trees to compare.
This is just an educated guess, but it looks right to me.
You should not simply take the files from under foo/_darcs/patches/ as
the concrete form of a patch depends on the permutations it has
undergone, and those might be different in your repo and in mine.
And that's also why I need to tell Darcs which repository I'm sending
the patch to... Thanks. I didn't think of that until you said it.
Cheers,
Daniel.
--
/\/`) http://oooauthors.org
/\/_/ http://opendocumentfellowship.org
/\/_/ No trees were harmed in the creation of this email.
\/_/ However, a significant number of electrons were
/ were severely inconvenienced.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
