bzr push after bzr branch

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
>> FWIW, I'm not a fan of pushing to the parent location as, imo, that's
>> not the bzr way. Instead, I'd suggest either:
>>
>> * Using a bound branch so commits implicitly go to both locations.
>>  That's idea for the local mirror (e.g. trunk) of a remote branch.
>>
>> * Merging from a local feature branch into your local trunk.
>>  Unlike push, merge will not screw up the mainline history of the
>>  branch being pushed to.
>>
>> I typically combine these, i.e. my trunk is nearly always a bound
>> branch, I branch from it to create feature branches and I merge those
>> back into the trunk.
> 
> Right, that's a great work flow for code branches, but doesn't make as much
> sense for $HOME dot-file and /etc files.   Those branches are almost never
> "branched-and-merged".  You just edit your files in place and then push them
> to a remote location for safe keeping.  That push location is (so far IME)
> always the same as the pull location.

Why not use a checkout for it then?

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktUcUQACgkQJdeBCYSNAAOqvgCgx/gcu/TgjICN2dcZcv8kpW1v
22sAoKN4KgkRzlYhPlnfCWmXTnUQXoxB
=ilOo
-----END PGP SIGNATURE-----