Thanks for the feed back Ingo. I've included the qbzr mailing list, and hence included your whole mail so they know what I'm talking about.
On Fri, Sep 25, 2009 at 3:30 PM, Ingo Strüwing <[email protected]> wrote: > Hi Gary, > > Gary van der Merwe, 23.09.2009 14:54: > >> On Wed, Sep 23, 2009 at 1:13 PM, Ingo Strüwing <[email protected]> >> wrote: >>> is there an option to let gcommit show unknown files together with the >>> changed files? >> >> >> Shameless plug: qcommit from qbzr can. > > Thanks again for the pointer. I did now have a chance to test qcommit > under life conditions. > > Since I don't know, where the "file comments" go, I started with gcommit > first (which I'm used to). I entered a revision coment and a couple of > file comments, cancelled with saved comments, and started qcommit. > > I didn't find any comment. :( The saving of comments between runs of a > commit tool is vital for me. So I can't use qcommit at this point in time. > > OTOH, I am happy about many improvements over gcommit: > > - qcommit remembers its geometry, at least the window size > (I would even more prefer size+position). > - qcommit provides a bunch of options in a context menu to every file. > - There may be a lot more, which I haven't detected yet. E.g. I've > not yet seen any contests in the "status" tab, so I don't know, > what it is good for. > > Disadvantages: > > - Doesn't load saved comments from [incomplete] preceding [un]commits. > - Doesn't automatically show file differences. Needs one extra click per > file. Perhaps this could be added as an option. The gcommit window > layout is very convenient to use to me. I like to see the differences > when writing the comments to each file. > - Doesn't remember the check in "show unversioned". > - Diff doesn't remember the diff type radio box setting. > > Suggestions: > > - To the file context menu, please add "remove" and "ignore" options. > - Please provide some doc that explains each element on the windows. > E.g. I can only guess that "fixed bugs" contains, what gcommit has > as per-file comments. But I don't understand, why it needs a check > box. If the doc is there already, please add a link to > http://bazaar-vcs.org/QBzr > > Regards > Ingo > -- > Ingo Strüwing, Database Group > Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten > Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel > Vorsitzender des Aufsichtsrates: Martin Häring HRB München 161028 > Ok - here goes :-) > Since I don't know, where the "file comments" go, I started with gcommit > first (which I'm used to). I entered a revision coment and a couple of > file comments, cancelled with saved comments, and started qcommit. >From the fact that you are using per file commit messages, I'm guessing you are a MySql dev :-). Currently we don't support per file commit messages. I hope to add that soon. https://bugs.launchpad.net/qbzr/+bug/380285 > - Doesn't load saved comments from [incomplete] preceding [un]commits. Um .. We do. Maybe you have a old version of qbzr, or maybe that's a bug. > - Doesn't automatically show file differences. Needs one extra click per > file. Perhaps this could be added as an option. The gcommit window > layout is very convenient to use to me. I like to see the differences > when writing the comments to each file. > - Diff doesn't remember the diff type radio box setting. Ok - good points. > - Doesn't remember the check in "show unversioned". That's by design. You typically don't have to add files very often. Again, thanks for the feed back. Regards, Gary -- bzr-gtk mailing list [email protected] Modify settings or unsubscribe at: https://lists.canonical.com/mailman/listinfo/bzr-gtk
