Can loggerhead be configured to display full paths for linked branches?

Asked by jrenbaum on 2009-08-28

We use links to development and release branches in order to control access. A basic view looks like:

root@bazaar-test:/var/new_bzr_repos# ls -al
drwxrws---+ 4 root client 4096 2009-08-28 15:35 client
drwxr-x--- 3 fred users 4096 2009-08-28 15:34 fred
drwxr-x--- 3 john users 4096 2009-08-27 16:32 john
drwxr-x--- 2 mike users 4096 2009-08-26 15:27 mike
lrwxrwxrwx 1 root root 18 2009-08-28 10:34 mrua_staging -> client/mrua/trunk/
drwxr-xr-x 3 roger users 4096 2009-08-28 14:23 roger

Users can referece mrua_staging and this works fine allowing us to change the link to a release branch when appropriate.

The problem is that Loggerhead simply lists mrua_staging as a branch at the top level. There is no way to know from the browser that the branch is really client/mrua/trunk.

Is there a way to configure Loggerhead to display this information or even some basic text description of a branch on the screen so that we could update this as needed?

Thanks,

Jay

Question information

Language:
English Edit question
Status:
Solved
For:
loggerhead Edit question
Assignee:
No assignee Edit question
Last query:
2009-10-07
Last reply:
2011-02-14

This question was reopened

There's no way to do this now, it would require a code change. A fairly simple and reasonably one, though!

Martin Pool (mbp) said : #2

2009/8/31 Michael Hudson <email address hidden>:
> Question #81245 on loggerhead changed:
> https://answers.edge.launchpad.net/loggerhead/+question/81245
>
>    Status: Open => Answered
>
> Michael Hudson proposed the following answer:
> There's no way to do this now, it would require a code change.  A fairly
> simple and reasonably one, though!

Can I suggest changing it into a bug for cases like this?

--
Martin <http://launchpad.net/~mbp/>

jrenbaum (jrenbaum) said : #3

Works for me. Looking forward to the next release and hoping its in there :~).

Thanks,

Jay

jrenbaum (jrenbaum) said : #4

Michael,

Based on your last response I thought that this would be turned into a bug, but I don't see it listed as a bug. Was that the intent? Is this being addressed and if so, when should I expect it?

Thanks,

Jay

Closing since there's an attached bug.