diff options
author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2022-09-04 11:27:06 +0100 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2022-09-04 12:36:11 +0100 |
commit | d6ce5696754c895926e122ed9b4690703dcdb78a (patch) | |
tree | f5d491efbfdca4bfe1d2aac3ebdd60cd3d8da375 /dgit-maint-debrebase.7.pod | |
parent | 2df2d6795e7ef7f34fb9a52236ecc9e8d40145fa (diff) |
docs: Update for changes to dgit push-*, and recommend push-source
In command line runes and examples, generally change to
"dgit push-source".
In running text whwere we talk about "push or push-source", change to
"push-built or push-source".
In running text where we talk loosely about "push", leave it that way.
Closes: #992606
Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Diffstat (limited to 'dgit-maint-debrebase.7.pod')
-rw-r--r-- | dgit-maint-debrebase.7.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/dgit-maint-debrebase.7.pod b/dgit-maint-debrebase.7.pod index b3700a4..6e19026 100644 --- a/dgit-maint-debrebase.7.pod +++ b/dgit-maint-debrebase.7.pod @@ -453,7 +453,7 @@ commits just as you would during B<git rebase -i>. After completing the git rebase, your branch will not be a fast-forward of the git HEAD you had before the rebase. This means that we cannot push the branch anywhere. If you are ready to upload, -B<dgit push> or B<dgit push-source> will take care of fixing this up +B<dgit push-source> (or B<dgit push-built>) will take care of fixing this up for you. If you are not yet ready to upload, and want to push your branch to a @@ -477,7 +477,7 @@ You can use dpkg-buildpackage(1) for test builds. When you are ready to build for an upload, use B<dgit sbuild>, B<dgit pbuilder> or B<dgit cowbuilder>. -Upload with B<dgit push> or B<dgit push-source>. Remember to pass +Upload with B<dgit push-source> or B<dgit push-built>. Remember to pass I<--new> if the package is new in the target suite. In some cases where you used B<git debrebase convert-from-gbp> since |