(hopefully https, but http or git will do)
for your packages' git repos.
These will be of the form:
-C<git-url>I<package-name>C<git-url-suffix>.
+C<git-url>B</>I<package-name>C<git-url-suffix>.
Configure:
B<ssh> I<localusername>B<@>C<push.git-host>
or
B<ssh> C<push.git-user-force>B<@>C<push.git-host>
+and expect to find the repos in
+C<push.git-path>B/>I<package-name>C<push.git-url-suffix>
Configure:
B<dgit-distro.>I<you>B</push.git-host> C<push.git-host>
dgit-distro.I<you>/push.git-user-force C<push.git-user-force>
-(eg you would set this too B<git> if your hosting service
+(eg you would set this to B<git> if your hosting service
expects every user to ssh to git@service)
C<dgit-distro.>I<you>B</push.git-proto> B<git+ssh://>
-C<dgit-distro.>I<you>B</push.git-path> "/dgit/I<you>/repos"
+C<dgit-distro.>I<you>B</push.git-path> C<push.git-path> (eg B</srv/dgit/>I<you>B</repos>)
+
+C<dgit-distro.>I<you>B</push.git-url-suffix> C<push.git-url-suffix> (if any)
=item git repository existence testing
+dgit needs to know how to check whether a particular package
+has a git repository yet.
+