bzr bundle > file

[Alexander Belchenko]

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

Martin Pool пишет:
> On 8/3/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
>> Jelmer Vernooij wrote:
>>> Hi,
>>>
>>> As of recently, "bzr bundle > file.diff" has broken - bzr now complains
>>> about using --output:
>>>
>>> bzr: ERROR: File must be specified with --output
>>>
>>> I tend to use this quite a lot, and I know other people do too. Is there
>>> a particular reason for forcing people to specify --output rather than
>>> defaulting to writing to stdout ?
>>>
>>> Cheers,
>>>
>>> Jelmer
>> Open bug:
>> https://bugs.launchpad.net/bzr/+bug/129504
>> https://bugs.launchpad.net/bzr/+bug/129724
>>
>> Basically, it is because of how we "upgraded" to use 'send' instead of
>> 'bundle'. And 'bundle' just became a deprecated alias of 'send'.
>>
>> We have 2 bugs open that indicate we want to restore the previous behavior,
>> though we will make 'bundle' a deprecated command.
>>
>> 'send' will eventually be a better command line interface, but we need to wean
>> people off of 'bundle' first.
>>
>> Oh, and you can do "bzr send -o- > file.diff". (so right now you can do the
>> same for bundle).
> 
> I think we really must restore the previous default of writing to
> stdout for bundle before releasing 19rc1.

What about format incompatibility?
Last stable format (v.0.9) was introduced year ago, and now we drop it
without any deprecation period. It's contradict to usual practice
in Bazaar for format bumps.

https://bugs.launchpad.net/bzr/+bug/129724

- --
[µ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGuAHzzYr338mxwCURAuAKAJ9wNLp+aHETBbJChVdCXOUePvw6KACfVysy
Jhw4/P2MxfIHQBOv+rZR8f0=
=WYo7
-----END PGP SIGNATURE-----