Hi.
I'm finding the TortoiseHg patch queue handling really frustrating. It seems
limited in ways which leave me wondering whether I've overlooked some major
feature, or I'm just not understanding it properly, or whether it's even
fully implemented at all
Firstly a minor niggle. The Patch Queue button does not toggle the Patch
Queue view, so once you have entered Patch Queue view there is no obvious
way to exit back to the normal repository view.
Now into the meat of it.
The Patch Queue view doesn't seem to work at all. I'm not sure what the
developers think it should do, but given that there is a list of patches on
the left side, a view for a patch commit message in the middle, and a view
for a patch diff on the right, I'd would expect that when I select a patch
from the list of patches that the patch commit message and patch diff views
would update to reflect data for the selected patch.
What actually happens though is that the diff displayed in the Patch Queue
view shows only the result of the combination of all applied patches, and
there appears to be no way to view the details of individual patches
(applied or unapplied) at all. Indeed if none of the patches in the queue
are applied you can't see anything at all.
The Graph Log view is the same. Only the last applied patch has any diff
associated with it and that also doesn't show the diff of the last applied
patch but the diff for the entire stack of applied patches.
So you have two different ways of seeing the diff of the entire stack of
patches, but no way at all of seeing the more useful (and necessary) view of
what each patch in turn does. It's very disconcerting to select patches in
the Patch Queue view and see no information about them, especially when you
have controls for applying patches in various orders, what use is that if
you can't even see what the patches are?
I also think it's rather dubious displaying unapplied patches in the Graph
log view at all. Unapplied patches do not get pushed so to my mind aren't
really part of the repository proper.
You have one UI element which is the Graph Log and another which is the
Patch Queue. It seems to me it would be far more understandable if there was
a clear differentiation between what was displayed by these elements, and on
first impression what would make most sense to me would be something like
this:
The Graph Log displays what's currently applied to the repository, so
changesets and applied patches only. Clicking on any patch there should
display only what that patch applied.
The Patch Queue view should list applied and unapplied patches and selecting
any of them should display the information for that patch only. If you want
to have a meta item in the Patch Queue list that displays the total effect
of all applied patches from that queue, then by all means that sounds like a
useful feature, but the current situation where that is _all_ you have
access to is imo not very useful at all.
Unless of course I'm missing something really obvious, which would not
surprise me in the least :)
Neutrino.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
