Sv: [darcs-users] Get started in Windows

[Steve Gardner]

On Tue, Sep 12, 2006 at 09:51,  Sven Grønlund wrote:

> 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


> Yes, I did the darcs record as stated in the "Getting started".
>
> 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? There seem to be a missing ling in
> the manual - or maybe I'm just too  slow!
>
> Kind regards
> Svend Grønlund
>
> --------- Original Besked --------
> fra: Miroslav Kure <kurem at upcase.inf.upol.cz <http://www.abridgegame.org/mailman/listinfo/darcs-users>>
> Til: darcs-users at darcs.net <http://www.abridgegame.org/mailman/listinfo/darcs-users> <darcs-users at darcs.net <http://www.abridgegame.org/mailman/listinfo/darcs-users>>
> Emne: Re: [darcs-users] Get started in Windows
> Dato: 12/09/06 15:10
>
> >/ 
> />/ On Tue, Sep 12, 2006 at 02:14:35PM +0200, Svend wrote:
> />/ > 
> />/ > I can create a repository and add some files; but how do I communicate
> /this
> >/ > first version to others?
> />/ 
> />/ You can just upload it on your web site and the others will *pull* your
> />/ version.
> />/ 
> />/ > I tried the darsc send command, but it insist on
> />/ > "No recorded local changes to send!"
> />/ 
> />/ First, did you do darcs record after adding the files?
> />/ Second, *where* are you trying to send the patches? There is no other
> />/ repository with your tree...
> />/ 
> />/ -- 
> />/ Miroslav Kure
> />/ 
> />/ _______________________________________________
> />/ darcs-users mailing list
> />/ darcs-users at darcs.net <http://www.abridgegame.org/mailman/listinfo/darcs-users>
> />/ http://www.abridgegame.org/mailman/listinfo/darcs-users
> />