add git utccommit recommendation to git guide

This commit is contained in:
idk
2021-03-05 16:14:20 -05:00
parent 573f33df2b
commit 9ef128721b

View File

@ -65,6 +65,14 @@ using the instructions on the home page.{%- endtrans %}</p>
</figure>
<h2 id="trans--fourth-attempt-a-clone--endtrans">{% trans -%}Fourth: Attempt a clone{%- endtrans %}</h2>
<p>{% trans -%}Now your tunnel is all set up, you can attempt a clone over SSH.{%- endtrans %}</p>
<p>{% trans -%}Git Privacy: Committing to git adds a timestamp to git commit messages, which may be configured to reflect your local time zone. To enforce the use of UTC for all commits, you are advised to use a git alias, such as: {%- endtrans %}
<pre><code>git config --global alias.utccommit '!git commit --date="$(date --utc +%Y-%m-%dT%H:%M:%S%z)"'</code></pre>
{% trans -%}which will allow you to substitute{%- endtrans %}
<pre><code>git commit</code></pre>
{% trans -%}for{%- endtrans %}
<pre><code>git utccommit</code></pre>
{% trans -%}in order to obscure your local time zone.{%- endtrans %}
</p>
<pre><code>GIT_SSH_COMMAND=&quot;ssh -p 7442&quot; \
git clone git@127.0.0.1:i2p-developer/i2p.i2p</code></pre>
<p>{% trans -%} You might get an error where the remote end hangs up unexpectedly. Unfortunately git still doesnt support resumable cloning. Until it does, there are a couple fairly easy ways to handle this. The first and easiest is to try and clone to a shallow depth: {%- endtrans %}</p>