Files view should show one-line change line per directory/file

Bug #240508 reported by Olav Vitters
4
Affects Status Importance Assigned to Milestone
loggerhead
Triaged
Low
Unassigned
loggerhead-breezy
Triaged
Low
Unassigned

Bug Description

The files view in Loggerhead should make the files view more usable by showing the last change for the file/directory.

For a file, this is easy. For a directory, it should figure out the most recent change made anywhere in that directory and show that. It already does this I think (with the revision number). However, it should also show the changes.

Compare e.g.
  http://svn.gnome.org/viewvc/mango/trunk/

To:
  http://bzr-mirror.gnome.org:9876/mango/trunk/files

Revision history for this message
Robert Collins (lifeless) wrote :

So there are a couple of topics in this bug. I agree that showing first line of the commit for files and directories is a better use of real estate than a 1-second granularity timestamp :).

For directories though, it does not scale well to find the last change anywhere within the tree (for a few internals-reasons). Essentially on something like openoffice each request would have to access data on up to 60 thousand revisions to decide which change within a subtree was the most recent. What is shown for directories today is the last change made to the directory itself - was it renamed/reparented/added.

We have discussed on the bazaar list having both direct-change and transitive-change fields for directories but to date that hasn't eventuated.

Personally I'd hesitate to do a transitive change field in loggerhead unless it either already has a cache that can answer the question without potential size_history data access, -or- a switch to enable it for trees that are of modest size (like gnome.org projects that are individually quite small).

I'm not sure about the usability impact of this, while I can see that seeing the last-change within a directory is nifty, its a single field - but you may often need to see the last three or four changes made within /directory/. For that the changes view, or a changes review restricted to a single directory, are better UI approaches IMNSHO.

Changed in loggerhead:
status: New → Confirmed
Revision history for this message
Martin Albisetti (beuno) wrote :

I think that just a link to it's latest revision is enough. Maybe there's other interesting information to show, but a small diff isn't it.

Changed in loggerhead:
status: Confirmed → Won't Fix
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Martin, this is about something more like log --line than a small diff, and I think that's at least worth exploring.

Changed in loggerhead:
status: Won't Fix → Triaged
Changed in loggerhead:
importance: Undecided → Low
Jelmer Vernooij (jelmer)
Changed in loggerhead-breezy:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.