Edgewall Software
Modify

Opened 11 years ago

Last modified 10 years ago

#11353 new enhancement

Hierarchical tree of repositories

Reported by: csa@… Owned by:
Priority: normal Milestone: next-major-releases
Component: version control/browser Version: 1.0.1
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

For a big project it would be really nice to organize git repositories into the hierarchical tree. Like

http://dside.dyndns.org/projects/screenshots/trac-repotree-small.png

I have hacked in a small patch for myself, but it will be really nice to have a proper implementation upstream. http://dside.dyndns.org/projects/patches.dir/trac-ds-repotree.diff

Attachments (0)

Change History (5)

comment:1 by Peter Suter, 11 years ago

Milestone: next-major-releases

comment:1:ticket:10480 and comment:4:ticket:10162 mention similar ideas, but I can't see an older ticket.

comment:2 by Ryan J Ollos, 10 years ago

Patch and image links are no longer valid. Would you kindly attach them to this ticket?

comment:4 by Peter Suter, 10 years ago

Thanks for providing the patch! I'm very interested in this feature. Can you share any experience you had with this patch?

E.g. I'm curious if there are any downsides to using /? (Given that that character can not appear in directory names.) How do you create such a repository? Are there no problems when checking out such a repo? Or how does that typically work?

Would e.g. _ be a useful alternative? (Or a similar approach as used by format=group and TitleIndex, where common WikiPageName prefixes are grouped hierarchically.)

Last edited 10 years ago by Peter Suter (previous) (diff)

comment:5 by anonymous, 10 years ago

The structure is built around directories. For example, the directory structure represented on the screenshot includes an ufo directory which contains number of repositories as subdirectories. The / is not actually used in the repository names. The / is only displayed because it was easier to make a patch this way. So, it would not influence access to the repos in any way.

ls -la ufo.git/
total 36
drwxr-xr-x 9 root root 4096 Feb 17 20:02 .
drwxr-xr-x 6 root root 4096 Mar  5 14:00 ..
drwxr-xr-x 7 root root 4096 Feb 17 20:00 concert
drwxr-xr-x 7 root root 4096 Feb 17 21:00 concert-examples
drwxr-xr-x 7 root root 4096 Jan  9 09:00 libuca
drwxr-xr-x 7 root root 4096 Feb 17 19:02 nexpy
drwxr-xr-x 7 root root 4096 Jan  9 09:00 ufo-core
drwxr-xr-x 7 root root 4096 Feb 17 15:00 ufo-filters
drwxr-xr-x 7 root root 4096 Jan  9 09:00 ufo-scripts

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.