will be passed on to git-buildpackage.
Tagging, signing and actually uploading should be left to dgit push.
will be passed on to git-buildpackage.
Tagging, signing and actually uploading should be left to dgit push.
See notes above regarding ssh and dgit.
NB that --gpg:option is not supported (because debsign does not
See notes above regarding ssh and dgit.
NB that --gpg:option is not supported (because debsign does not
plus appropriate diffs and cherry picks from the dgit remote tracking
branch, construct a git commit whose tree corresponds to the tree to use for the
next upload. If that commit-to-be-uploaded is not a descendant of the
plus appropriate diffs and cherry picks from the dgit remote tracking
branch, construct a git commit whose tree corresponds to the tree to use for the
next upload. If that commit-to-be-uploaded is not a descendant of the
.BR "git merge -s ours remotes/dgit/dgit/" \fIsuite\fR;
that tells git that we are deliberately throwing away any differences
between what's in the archive and what you intend to upload.
.BR "git merge -s ours remotes/dgit/dgit/" \fIsuite\fR;
that tells git that we are deliberately throwing away any differences
between what's in the archive and what you intend to upload.
\fBgit-buildpackage\fP(1),
\fBdpkg-buildpackage\fP(1),
.br
\fBgit-buildpackage\fP(1),
\fBdpkg-buildpackage\fP(1),
.br