Re: HACKING: More usage hints regarding 'bootstrap'

[Jose E. Marchesi]

> These days I have local changes to gnulib and jitter, and
> 'bootstrap' repeatedly attempts to erase them. Worth documenting.
> Here is a proposed patch.

This has also happened to me :)
OK for master.
Thanks!

>
>>From 4021bd0f7390c71ba7086cd87241cb836be56937 Mon Sep 17 00:00:00 2001
> From: Bruno Haible <bruno@clisp.org>
> Date: Sun, 21 Feb 2021 22:51:56 +0100
> Subject: [PATCH] HACKING: More usage hints regarding 'bootstrap'.
>
> * etc/hacking.org: Explain how to preserve local changes to gnulib or jitter,
> despite bootstrap.
> ---
>  etc/hacking.org | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/etc/hacking.org b/etc/hacking.org
> index eff9e7d..b595b22 100644
> --- a/etc/hacking.org
> +++ b/etc/hacking.org
> @@ -266,6 +266,14 @@ Mohammad-Reza Nabipoor   <m.nabipoor@yahoo.com>
>     You can't rely on the maintainer-mode rules there, because of
>     certain problem with the sub-package mode of Jitter.
>  
> +** Building with local changes to gnulib or jitter
> +
> +   If you have local changes to gnulib or jitter, that are not yet
> +   register as submodule reference commits, the way to invoke bootstrap
> +   such that it doesn't delete your changes is:
> +
> +   : $ ./bootstrap --skip-po --no-git --jitter-srcdir=jitter
> +
>  ** Gettext
>  
>     When updating gettext, besides the normal installation on the