(fwd) bzr shelve feedback

[Brad Bollenbach]

Le 29-Nov-05 à 10:14 PM, James Blackwell a écrit :

> On Thu, Nov 24, 2005 at 10:53:41AM -0500, Brad Bollenbach wrote:
>>> And since shelve/unshelve are part of the bzrtools plugin, not bzr,
>>> it's not appropriate to file a bug against bzr.
>>
>> Like most new bzr users, I have no idea about this distinction. :) To
>> be honest, I'm not really interested in caring about this distinction
>> either. (This reminds me of the time that we accidentally expected
>> Launchpad users to distinguish "Soyuz" from "Launchpad" when filing
>> bugs. :)
>
> Hmmm. How did shelve get on your system?  You can imagine shelve as  
> a 3rd
> party prototype of what some day could be directly in bzr someday.  
> Right
> now its not part of bzr while kinks are worked out.

It got on my system by following these instructions:

     https://wiki.launchpad.canonical.com/RocketFuelSetup

For the bzr implementor or someone who has already spent some time  
reading through documentation, I bet this distinction between what is  
plugin and what is core is obvious. Just like the distinction between  
Soyuz, Malone, Rosetta and FOAF is obvious to me where, in practice,  
users' Launchpad bug reports have demonstrated that they are  
generally unable to (and with good reason) make that distinction.

>> In slightly over a year of working on Malone, though I've used baz
>> undo many times, I was never particularly bothered by not being able
>> to pick things apart hunk by hunk.
>
> I have. Did you ever merge something with local work, and you  
> needed to
> save that local work? shelve can help with that.

I probably accidentally did that once or twice, yes. But normally I  
would first undo, then merge and commit, then redo and proceed. :)

Cheers,

--
Brad Bollenbach