>>>>> "stefan" == Stefan Reichör <[EMAIL PROTECTED]> writes:
stefan> Hi Vincent!
>> Cough, the following is simpler:
stefan> Thanks - that is much easier to grasp.
>> BASE=~/src/bzr/reviews
>> NICK=$1
>> PATCH=$BASE/$NICK.diff
>> cd $BASE
>> bzr init $NICK
>> cd $NICK
>> bzr pull $PATCH
stefan> I am not sure, if I fully understand the sequence.
stefan> What do you get per mail?
stefan> Is it just a simple diff?
stefan> Is it a bundle (or whatever it is called in bzr)?
A bzr bundle produced by bzr send. It contains all the
information needed to reconstruct the branch it was send from.
Roughly speaking, you branch from a trunk, hack, hack, commit,
bzr send (which can either send a mail directly or create a fail
suitable to be attached to a mail, see bzr help send (and ask for
clarifications if needed :)).
On the receiving side, you save the bundle as bundle.diff (or
bundle.patch, whatever).
Then you can either:
- bzr merge bundle.patch (in an existing branch sharing some
ancestry with the bundle),
- bzr init new & bzr pull -d new bundle.patch
I prefer the later because it gives me an exact copy of the
sender branch, but the former gives you a branch with the
modifications installed as well (modulo the possible conflicts).
stefan> bzr init $NICK initializes a new repository
stefan> Is this correct?
No, it initializes a branch (bzr init-repo initializes a
repository).
stefan> Or do you have some kind of shared layout?
Yes I do have a shared repository at ~/src/bzr/.bzr, so that any
'bzr init' or 'bzr branch' issued below ~/src/bzr will use it.
But this is bzr stuff, the script itself doesn't care, it just
does bzr init and depending on the location it will use a shared
repository or creates a new one inside the branch.
Vincent
_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev
