RFC: TortoiseBzr strategies

[Robert Widhopf-Fenk]

On Saturday, March 29, 2008 at 10:15:27, Mark Hammond wrote:
> Paul Moore writes:
> 
> > I'd like to retain an installation option (either a separate
> > installer, or more sensibly an option in a single "blessed"
> > installer) to just install a command line version, exactly as the
> > current bzr. Not all Windows users want to use a GUI for
> > everything :-)
> 
> Definitely.  Many developers that use Windows don't treat it much
> differently than we do other operating systems.  Personally I have
> never used any of the tortoise tools, simply as find the
> command-line more productive for almost everything I do. 

The command line is not at all productive for everything.

After doing changes I want to view them in their context,
i.e. the base revision side by side to the working copy as
this provides then full context no just three lines like the
diff.

  bzr diff --diff-options=--side-by-side | less

is no match for ediff or TortoiseMerge.

Then quite often I am doing partial reverts of (debug) code
or set aside some hunks (sometime is also use shelve) in
this "diff"-view.  It is just tedious to do this in the
source editor and run "bzr diff" again and again in order to
check if the changes have been reverted correctly.

Finally, I am doing selective commits for unrelated changes.
Hey, three clicks are shorter than typing three file names.

When browsing the history (searching for the cause of a bug
etc.) it is also much easier to find relevant revisions and
get instant access to the list of changed files and the
diffs.

With BZR I use DVC in Emacs most of the time and for SVN I
use Tortoise for these and I do not see any way to be more
productive on the command line.

I wonder if you are more productive for them on the command
line, but maybe you have a different workflow and never do
these tasks?

Bye Robert