Hello Stefan,
the use case is as follows:
The projects consists of circa 18 IP cores. Each IP core is represented by a
Git repository. Think of an IP core as of a lonestanding DLL or SO file
project. Each IP core references 2 submodules, which bring the verification
environments for testing the IP core standalone.
These 18 IP cores are grouped to bigger IP cores, referencing the low-level IP
cores and each again the 2 verification submodules. Finally, the main project
references the bigger IP cores and again the 2 verification cores.
TOPLEVEL
o- IP1
o- UVVM
o- VUnit
o- IP2
o- UVVM
o- VUnit
o- IP3
o- UVVM
o- VUnit
o- IP4
o- UVVM
o- VUnit
o- IP5
o- UVVM
o- VUnit
o- IP6
o- UVVM
o- VUnit
o- IP7
o- UVVM
o- VUnit
o- IP8
o- UVVM
o- VUnit
o- IP9
o- UVVM
o- VUnit
o- IP10
o- UVVM
o- VUnit
o- IP11
o- UVVM
o- VUnit
o- IP9
o- UVVM
o- VUnit
o- IP12
o- UVVM
o- VUnit
o- UVVM
o- VUnit
That's the simplified structure. I can't write more, because it's a closed
source project. You can find other usecases e.g. in my other open source
projects. E.g. The PoC-Library or The PicoBlaze-Library and the corresponding
PoC-Examples repository.
Example: PoC
Pile of Cores includes 4 Git submodules and is itself an IP core library.
So PoC-Examples again references PoC. This looks like this tree:
PoC-Examples
|- lib/
o- PoC
|- lib
o- Cocotb
o- OSVVM
o- VUnit
o- .... OSVVM
o- UVVM
The library VUnit itself already includes OSVVM as a library.
----------------------
Forcast:
I'll write a new question / idea about multiple equal submodules and the memory
footprint soon...
Here is my original question posted on StackOverflow:
https://stackoverflow.com/questions/44585425/how-to-reduce-the-memory-footprint-for-multiple-submodules-of-the-same-source
----------------------
Do you need more use cases?
Kind regards
Patrick
________________________________________
Von: [email protected] [[email protected]]" im Auftrag von
"Stefan Beller [[email protected]]
Gesendet: Montag, 19. Juni 2017 19:47
Bis: Patrick Lehmann
Cc: Lars Schneider; Git Mailinglist
Betreff: Re: Restoring detached HEADs after Git operations
On Mon, Jun 19, 2017 at 10:34 AM, Patrick Lehmann
<[email protected]> wrote:
> Hello,
>
> I'm just an advanced Git user, not a Git developer. So I might find some time
> to improve the suggested script, which I provided with the hints given on the
> mailing list, but I have no time to do a complete feature release in your
> patch based Git flow.
ok, thanks for letting us know. I may re-prioritize the "reattach
HEAD" patches that I referenced earlier.
I would have hoped that additionally to the shell lines you'd have
given a good use case/summary.
> I have no experience with other shells then Bash. So if you rely on a Bash
> with less features, please port the syntax to such a shell system. (I
> personally do not support legacy programs or out-date programs).
>
> ------
> We are talking about circa 50 submodules in total with a maximum depth of 4.
> The platforms are:
> - Mint OS with Git in Bash
> - Windows 7 with Git-Bash
> - Windows 10 with Git-Bash
> - Windows 10 with Posh-Git
Thanks,
Stefan
