unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Height of Unicode chars is not right
Date: Wed, 23 Sep 2015 22:06:22 +0300	[thread overview]
Message-ID: <83lhbxj6q9.fsf@gnu.org> (raw)
In-Reply-To: <d39a5e2a-eeb3-4475-bee5-2109997d23b7@googlegroups.com>

> Date: Wed, 23 Sep 2015 10:19:35 -0700 (PDT)
> From: Rusi <rustompmody@gmail.com>
> 
> I tried again with --depth 1 (shallow clone)
> Shallow emacs 262M
> Full clone 441M
> 
> In particular
> shallow emacs' .git 38M
> Full emacs .git 228M
> 
> Most important it was some 2 hours yesterday with full and less than ½ with shallow
> 
> So people setting out to build their own should probably be recommended to
> use --depth 1 ??

No, you are well advised to use full.  Those 2 hours are a one-time
cost, the subsequent updates are much faster.




      parent reply	other threads:[~2015-09-23 19:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:13 Height of Unicode chars is not right Rusi
2015-09-22 15:45 ` Grant Rettke
2015-09-22 15:50   ` Óscar Fuentes
2015-09-22 15:59   ` Sergey Organov
     [not found]   ` <mailman.1606.1442937082.19560.help-gnu-emacs@gnu.org>
2015-09-22 16:08     ` Rusi
2015-09-22 16:41       ` Eli Zaretskii
2015-09-22 17:27         ` Rasmus
2015-09-22 16:52       ` Óscar Fuentes
2015-09-22 17:05         ` Eli Zaretskii
2015-09-22 17:12           ` Óscar Fuentes
2015-09-22 17:31             ` Eli Zaretskii
     [not found]         ` <mailman.1615.1442941512.19560.help-gnu-emacs@gnu.org>
2015-09-22 17:10           ` Rusi
     [not found]       ` <mailman.1610.1442940060.19560.help-gnu-emacs@gnu.org>
2015-09-23  1:57         ` Rusi
2015-09-23  6:47           ` Eli Zaretskii
     [not found]           ` <mailman.1638.1442990857.19560.help-gnu-emacs@gnu.org>
2015-09-23 17:19             ` Rusi
2015-09-23 19:05               ` Óscar Fuentes
2015-09-23 19:06               ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lhbxj6q9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).