One of the commands in my previous email was incorrect: instead of
"darcs send --context=\D.context --output=\mywork.bundle"
it should be
"darcs send --context=\D.context --output=\mywork.bundle ."
(with a "." at the end). Sorry about that.
The first version worked when I tested it, but that was only
because I had a _darcs\prefs\defaultrepo file. The repository
specified in that file had no relevance to the result, though, which
leads me to suggest that "darcs send" is wrong to require a repository
when both "--context" and "--output" are specified.
Do others agree?
Best regards
Steve Gardner
--
On Wed, Sep 13, 2006 at 05:51 EDT, Steve Gardner wrote:
On Tue, Sep 12, 2006 at 09:51, Svend Grønlund wrote:
(spelling corrected)
Then you talk about another repository? Well, I imagine, that somehow I
should let other developers have a copy of my newly created, not yet
changed, repository? Or should they just have a copy of the files,
and then
create their own repository the same way?
You can all just run "darcs init" in empty directories. After that,
you can start recording and sending patches.
The "No recorded local changes to send!" message you saw was not very
accurate. It should have been something like:
"I can't send without knowing what is in the destination repository"
Below are some tips on using darcs in a low-tech way, without a
web server, using email attachments to exchange bundles of patches
that are applied manually using "darcs apply".
If you just want to send a bundle of patches to another developer
(called "D") as an email attachment, you need to tell "darcs send"
about the state of D's repository.
You could keep a local mirror of D's repository (say, in directory
\D), and use "darcs send --output=\mywork.bundle \D". Then you can
email the bundle to D. Once D has applied it, you can update your
mirror with "darcs push \D".
An alternative to maintaining a mirror of D's repository is to keep a
context file - created using "darcs changes --context > \D.context" at
times when your repository matches D's. Then, after recording changes,
you can make a bundle with
"darcs send --context=\D.context --output=\mywork.bundle". Once D has
applied it, update the context with
"darcs changes --context > \D.context" again.
We use the context file method and find it very effective. One problem
we had was email clients corrupting bundles. To get around this, we
compress the bundles (using 7-Zip on Windows) before sending.
I hope this is useful
Best regards
Steve Gardner
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
