dpush command in bzr-svn

[Jelmer Vernooij]

Hi Russel,

Russel Winder wrote:
> On Sun, 2009-03-22 at 22:11 +0100, Jelmer Vernooij wrote:
>> Hi Russel,
>>
>> Russel Winder wrote:
>>> I see you have removed the dpush command from bzr -svn. Has it already
>>> appeared somewhere else or do I need to revert my bzr-svn branch to
>>> reinstate the command.
>>>   
>> Yeah, it's been removed in preparation of it being included in bzr.dev 
>> or (if it is rejected for inclusion in bzr.dev) moved to a separate 
>> plugin. See this patch in bundlebuggy:
>>
>> http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C49C6A5B7.1050105%40vernstok.nl%3E
>>
>> The reason I've removed it at this point is that bzr-git also supports 
>> dpush and I didn't want bzr-git to depend on bzr-svn or vice-versa and 
>> keeping three copies of dpush up-to-date (one in bzr-git, one in bzr-svn 
>> and one in the patch for bzr.dev linked above) is too much work.
> 
> The problem is that by removing dpush from bzr-svn before it appears
> either as a separate plugin or in bzr.dev then people that use the
> command are put in a "I can't do any work" situation :-(
> 
> I reverted my branch of bzr-svn back one commit so I have a working
> dpush but it means I cannot follow any further changes in the branch.
Unfortunately things like this may happen from time to time when using
development versions of bzr or the plug, just like plugins will print
deprecation warnings during the development cycle.

The best way to avoid these problems is to stick with a released version
of Bazaar and the plugins; this can sometimes unfortunately mean waiting
 longer (up to a month) before  you can use bug fixes that have landed.

Cheers,

Jelmer