[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
[an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]![]() |
![]() |
![]() |
|||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
![]() |
![]() |
![]() |
2013/4/8 Peter Makholm <sslug@sslug>: > Jens Bang <sslug@sslug> writes: > >> Hvad gør I der ude med kode der deles mellem flere projekter? Specielt >> når der er tale om kode der stadig er under udvikling. >> [...] > Som udgangspunkt ville jeg jeg håndtere det som et helt separat > projekt. Det betyder at projektet har sit eget git-repository, > byggesystem og sin egen versionscyklus. Ja. I git hedder det submodules og kan anbefales. Se f.eks. http://git-scm.com/book/en/Git-Tools-Submodules /Martin
![]() |
![]() |
![]() |
||||||||||||
|
||||||||||||||
![]() | ||||||||||||||
|
||||||||||||||
![]() |
![]() |
![]() |