Tommy Pettersson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> 1) create a temporary branch with: darcs get --to-patch "^\[project
> @ 126\]$"
>
> 2) create the (first) tag in this temporary branch with: darcs tag
> version-1-10.1
>
> 3) push the (first) tag to the "master" repo with: darcs push
>
> 4) either use 'darcs pull' to pull patches from the master repo up
> to the next version, or remove the temporary branch and redo
> step 1 with another --to-patch regexp.
>
> 5) repeat from step 2
>
>
> Please ask again if this is to terse or unclear.
Hi Tommy,
thanks for your answer; it worked (almost) like a charm.
There was one oddity in the process: at the end of all the pulls from the
original repository, Darcs asked me if I wanted to pull several tags I just
did (and pushed as of step 3). I answered yes, out of puzzlement, and ended up
with duplicate tags in my changes.
So I started again, but this time, didn't push anything to the original
repository and all went well (I now simply consider the new repository as the
main one).
This also brings me two other questions:
1/ After the process, I pushed my new repository to the old one, which made
the tags appear in the changes, but last. I thought that `darcs optimize
--reorder-patches` would place them at the expected place in the history
(meaning, right after all the patches they depend on), but no. They're still
appearing last. Is it normal ? I guess it is, but it's surprising.
2/ When tagging, I also used the --checkpoint flag for people to be able to
optimally retreive just stable versions. I couldn't find a way to display, for
a given repository, the places where checkpoints are placed. Is there one ?
Thanks again.
--
Looking for a Christmas present idea? http://cdbaby.com/cd/didierverna
Didier Verna EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
