List for cgit developers and users
 help / color / mirror / Atom feed
From: list at eworm.de (Christian Hesse)
Subject: Nesting repositories under a common folder?
Date: Wed, 24 Jul 2019 20:40:49 +0200	[thread overview]
Message-ID: <20190724204049.3bae5dbf@leda> (raw)
In-Reply-To: <CAB-aZK-A9PL_P2tBqHwYx4xR8RD8e3433fifX-B3OpawS0Ks-Q@mail.gmail.com>

Reuben Popp <reuben.popp at gmail.com> on Wed, 2019/07/24 13:01:
> Hello all,
> 
> Excuse me if this has been answered before, but is there a way to nest
> repositories under a common directory visually in cgit?
> 
> For example,
> 
> root_directory (not a repo)
> |- Project A (directory, not a repo)
> |       |- Project A component 1 (repo)
> |       |- Project A component 2 (repo)
> |- Project B (repo)
> |- Project C (directory, not a repo)
> |       |- Project C subproject AA (repo)
> |       |- Project C subproject AB (repo)
> |       |- Project C Archive (directory, not a repo)
> |              |- Project C archived subproject A (repo)
> etc.
> 
> Going to the cgit frontend, I would see the directories (or links) for
> Project A, B and C...

Are you searching for something like config option section-from-path? That
allows just one level, though.
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20190724/9a5f96a0/attachment.asc>


  reply	other threads:[~2019-07-24 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 18:01 reuben.popp
2019-07-24 18:40 ` list [this message]
2019-07-24 18:43 ` john
2019-07-24 19:05   ` reuben.popp
2019-07-24 19:44     ` john

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190724204049.3bae5dbf@leda \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).