rename push to publish

[John A Meinel]

Robert Collins wrote:
> This came out of a conversation with aaron:
> 
> Some people want 'push B' to be equivalent to 'cd B; pull $LASTCWD'.
> Others dont.
> 
> I define them as pull is 'update to be like that other branch but keep
> my preferences etc' and push is 'publish my branch precisely for others
> to use'
> 
> (right now there are bugs that make push not be precisely that, but its
> not the inverse of pull).
> 
> If we add '-d LOCATION' which arch had and was very useful (could choose
> a different letter, -d was for 'directory'), one could do
> 'bzr -d sftp://foo/bar/gam pull $(pwd)' to mean 'cd to
> sftp://foo/bar/gam and pull from $(pwd)' - even though one cannot
> physically cd there, we can do so in a logical sense within bzrlib.
> 
> So aaron suggested renaming push to publish and using that -d for anyone
> that wanted the inverse of pull behaviour (such as setting the remote
> 'parent' to $pwd, which IMO is nuts for a copy of my branch on a
> webserver.

If we continue to have 'push' able to create branches, then I think it
should be called 'publish'. Ultimately, I think this functionality
should be in 'branch' not in 'push'.

I would really like to keep 'push' as semi-reverse process of 'pull'. As
I think it is easy to remember, and intuitive. It doesn't have to be
identical to 'cd $foo; bzr pull', because there will be minor
differences in what it means to push versus pull. But I don't see why
'bzr push' would change the remote locations preferences to look like my
local preferences (it obviously shouldn't set 'parent').

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060210/ec3af567/attachment.pgp