[MERGE] dpush / foreign vcs testing

[Jelmer Vernooij]

Martin Pool wrote:
> 2009/4/4 Ben Finney <ben+bazaar at benfinney.id.au>:
>> Jelmer Vernooij <jelmer at vernstok.nl> writes:
>>
>>> Can you suggest a better name? I agree the current name is not very
>>> clear, but I can't think of anything that covers what it does
>>> better.
>>>
>>> dpush pushes into a foreign vcs but without storing bzr semantics
>>> that can't be represented in the remote system. So in the case of
>>> bzr-svn it doesn't set any bzr-specific revision or file properties.
>>> In the case of git it for example doesn't store any rename
>>> information.
>> I would expect this to be an option for ‘push’. Suggestions: ‘push --foreign-clean’ or ‘push --foreign-only’
> 
> Yes, if it's "pushes but without xxxx" then an option to push seems
> appropriate.  I think just 'dpush' is always going to make people
> wonder what the d stands for, and whether they can or should use it
> pushing to another branch - in fact yet another person just asked off
> the list.
> 
> Also, it seems like if this were an option you might like to set it in
> locations.conf for the url of the foreign branch, and then after
> configuring that you could just use push without worrying about it.
> It may be worth emitting a note explaining what's happening when
> that's active (like "pushing to svn without bzr metadata" or
> something).
The main reason I've made dpush into a separate command is because it
violates one of the core invariants of push: it changes the source branch.

I'm not necessarily opposed to have it as an option to push, but I think
this aspect should be clearly expressed. Aaron's suggested "bzr push
--lossy" seems to do this somewhat, but doesn't express that the source
branch is changed as well. The --no-rebase option would have to be
renamed too.

Cheers,

Jelmer