[PATCH general-docs] improve notes on pushing to Bitbucket
Mike Kupfer <[email protected]> Thu, 19 Nov 2015 18:06:39 -0800
| Newsgroups | gmane.emacs.xemacs.patches |
|---|---|
| Message-ID | <[email protected]> |
This tweaks some text from my earlier DevGuide patch, in response to feedback from Henry Thompson (thanks, Henry!). I'll apply this late next week if nobody objects. mike 2015-11-19 Mike Kupfer <[email protected]> * texi/xemacs/xemacs-devguide.texi: (Getting Started as a Package Maintainer): Add the option of using an https URL for pushing to Bitbucket. Note that an ssh key is needed for an ssh URL. diff --git a/texi/xemacs/xemacs-devguide.texi b/texi/xemacs/xemacs-devguide.texi --- a/texi/xemacs/xemacs-devguide.texi +++ b/texi/xemacs/xemacs-devguide.texi @@ -10,9 +10,9 @@ @c Developer's Guide variables. @set DEVGUIDE @cite{XEmacs Developer's Guide} -@set EDITION 0.8 -@set UPDATED 2015-08-16 -@set UPDATE-MONTH August, 2015 +@set EDITION 0.8.1 +@set UPDATED 2015-11-19 +@set UPDATE-MONTH November, 2015 @c Other variables. @set XEMACSORG XEmacs.ORG @@ -974,13 +974,28 @@ interdependencies are frequent. The next step is to configure any packages that you want to change so -that they can be pushed back to Bitbucket. In the @file{.hg/hgrc} for -each such package, change the https URL to an ssh URL, i.e., +that they can be pushed back to Bitbucket. Two approaches have been +shown to work: ssh, and https with your Bitbucket login. + +For ssh, you will need to register an ssh public key at Bitbucket. On +many systems you can generate a key pair using the @command{ssh-keygen} +command. You will also need to change the @code{default} line in the +@file{.hg/hgrc} for each package to @example default=ssh://hg@@bitbucket.org/xemacs/@var{package_name} @end example +For https, change the @code{default} line in the +@file{.hg/hgrc} for each package to + +@example +default=https://@var{login}@@bitbucket.org/xemacs/@var{package_name} +@end example + +@noindent +where @var{login} is your Bitbucket login name. + The package developer is welcome to change anything in the repo for his or her package. However, there are a couple of administrative