Max Kanat-Alexander wrote:
> I had a chat with lifeless about this on #bzr, and actually, yes, you're
> right, from bzr's perspective, those are valid conflicts.
>
> So really, what I want is simply a better way to do what I'm trying to
> do. There actually isn't anything in bzr that does the same as "cvs up"
> would do--partly because CVS customizations are usually uncommitted, and
> bzr customizations are committed. Here's what I've told people to do for
> now:
>
> http://groups.google.com/group/mozilla.dev.apps.bugzilla/browse_thread/thread/358ed7399bf0a1f3
>
Switch seems like it would be pretty close. (Change my underlying
revisions to match this other revision, but preserve my uncommitted
changes.)
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Max Kanat-Alexander wrote: groups. google. com/group/ mozilla. dev.apps. bugzilla/ browse_ thread/ thread/ 358ed7399bf0a1f 3
> I had a chat with lifeless about this on #bzr, and actually, yes, you're
> right, from bzr's perspective, those are valid conflicts.
>
> So really, what I want is simply a better way to do what I'm trying to
> do. There actually isn't anything in bzr that does the same as "cvs up"
> would do--partly because CVS customizations are usually uncommitted, and
> bzr customizations are committed. Here's what I've told people to do for
> now:
>
> http://
>
Switch seems like it would be pretty close. (Change my underlying
revisions to match this other revision, but preserve my uncommitted
changes.)
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAku /T3EACgkQJdeBCY SNAAO4DwCgs3WcB MJZUJby9DnUJecI NSCK nOYBDSJkko+ KeivV9
eL0An3sNiUBQEdh
=AfeG
-----END PGP SIGNATURE-----