chiark / gitweb /
dgit-maint-merge(7): Mandate pushing upstream branch to alioth
authorSean Whitton <spwhitton@spwhitton.name>
Sun, 26 Nov 2017 00:23:07 +0000 (17:23 -0700)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sat, 6 Jan 2018 01:24:14 +0000 (01:24 +0000)
commitcb9da2c5c7e3c05adb78b682685a0fe0357958e0
treead7d252a6d37d0ecc5e12bd43f1a7cd0c7ef525c
parent1ea867d81b069b145a9e1b7a38c97e99e1c40e4f
dgit-maint-merge(7): Mandate pushing upstream branch to alioth

In the case where we are using gbp-import-orig(1) to maintain a
virtual upstream branch, we must push that branch somewhere.  It is
needed whenever we import a new upstream release.

Thanks to Johannes Schauer for pointing out that the manpage
previously said that pushing to alioth is always optional.

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
dgit-maint-merge.7.pod