down-thread complains about "uncommited changes" without describing them or workarounds

[Torsten Bronger]

bzr-loom complains about spurious uncommited changes:
--------
bronger@wilson:~/src/packages$ bzr init --2a felo
Created a standalone tree (format: 2a)
bronger@wilson:~/src/packages$ cd felo
bronger@wilson:~/src/packages/felo$ bzr nick upstream
bronger@wilson:~/src/packages/felo$ bzr loomify
bronger@wilson:~/src/packages/felo$ bzr create-thread debian
bronger@wilson:~/src/packages/felo$ bzr down-thread
bzr: ERROR: Working tree has uncommitted changes.

-----

the tree has a change - the tree root has been added.

[Robert Collins (lifeless)]

This was added based on user experience. There is another command,
switch, which will preserve changes.

From 'bzr help down-thread':
...
Down-thread refuses to operate if there are uncommitted changes, since
this is typically a mistake. Switch can be used for this purpose,
instead.
...

We could add a --force parameter/ --no-strict parameter to down-thread
too. What do you think, will switch be convenient?

-Rob

[Aaron Bentley (abentley)]

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

Robert Collins wrote:
> This was added based on user experience. There is another command,
> switch, which will preserve changes.

I think the complaint is that it's not clear that there is an
uncommitted change-- the versioning of the tree root.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEUEARECAAYFAkp8wMoACgkQ0F+nu1YWqI1phwCUDctEsZgXzrtj2mMqjYoEKM4R
oACaAgURpd1oVYWoijLKGR5i7f5dnTY=
=PDa1
-----END PGP SIGNATURE-----

[Robert Collins (lifeless)]

On Sat, 2009-08-08 at 00:03 +0000, Aaron Bentley wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Robert Collins wrote:
> > This was added based on user experience. There is another command,
> > switch, which will preserve changes.
>
> I think the complaint is that it's not clear that there is an
> uncommitted change-- the versioning of the t

Oh. Hmm, perhaps the output should be
"cannot down-thread with uncommitted changes:
<bzr status output>
"

?

[Aaron Bentley (abentley)]

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

Robert Collins wrote:
> On Sat, 2009-08-08 at 00:03 +0000, Aaron Bentley wrote:
>> I think the complaint is that it's not clear that there is an
>> uncommitted change-- the versioning of the t
>
> Oh. Hmm, perhaps the output should be
> "cannot down-thread with uncommitted changes:
> <bzr status output>
> "
>
> ?

That wouldn't help, because the status output ignores the tree root.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkp8zJAACgkQ0F+nu1YWqI1fwwCdHplkdblJKWiIgpZ5afgduekq
a44AnREY/YWPoQvn7U1a2p47AK9X4cRx
=DbKb
-----END PGP SIGNATURE-----

[Robert Collins (lifeless)]

Do you have any suggestions about how to improve the situation?