From 9f20a18c1d4228b46c6366c86643ba357c218f96 Mon Sep 17 00:00:00 2001 From: Tails developers Date: Sat, 2 Aug 2014 17:05:18 +0000 Subject: [PATCH] Salvage content from #5506. --- wiki/src/blueprint/Git_sub-repositories.mdwn | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 wiki/src/blueprint/Git_sub-repositories.mdwn diff --git a/wiki/src/blueprint/Git_sub-repositories.mdwn b/wiki/src/blueprint/Git_sub-repositories.mdwn new file mode 100644 index 00000000000..acbc926fde1 --- /dev/null +++ b/wiki/src/blueprint/Git_sub-repositories.mdwn @@ -0,0 +1,20 @@ +**Corresponding ticket**: [[!tails_ticket 7036]] + +A few teams, such as the debian-installer and Debian Perl ones, that +use many Git repositories (thousands, in case of the latter), have +been successfully using mr to make an initial checkout easier for new +contributors, and generally making it easier to deal with a lot of +repositories (mass-update, etc.). We could do the same, starting with +maintaining and publishing a .mrconfig file. + +Additional custom repositories we use and may want to include in this +.mrconfig: whisperback, htp, tails-greeter, etc. + +OTOH, Git submodules allow to do basically the same thing, but also to +make it clear what version of these other repositories a given Git +branch (in the main repo) needs. + +Ressources: + +* [d-i help page](http://wiki.debian.org/DebianInstaller/CheckOut) +* [pkg-perl help page](http://pkg-perl.alioth.debian.org/git.html) -- 2.11.4.GIT