From: Harald Hanche-Olsen <hanche@math.ntnu.no>
To: stephen.berman@gmx.net
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: need help adjusting workflow to git (or vice versa)
Date: Thu, 13 Nov 2014 21:58:27 +0100 (CET) [thread overview]
Message-ID: <20141113.215827.2302048163561451721.hanche@math.ntnu.no> (raw)
In-Reply-To: <87k32yu8yh.fsf@rosalinde.fritz.box>
[Stephen Berman <stephen.berman@gmx.net> (2014-11-13 20:44:22 UTC)]
> That's what Martin referred to, isn't it? It takes considerably longer
> on my older and feebler hardware, also compared with `bzr update' and
> `bzr pull --overwrite' in a shared repository. And the size is also not
> insignificant, if it means having a copy of the entire Emacs repository
> for each build (~540M).
You might have a look at the options --local and --shallow to git
clone. The idea would be to have one full clone that pulls from
savannah, then any number of local clones pulling from from that one.
After running git clone --local emacs emacs2
I get this:
; du -sh emacs/.git emacs2/.git
199M emacs/.git
392K emacs2/.git
The clone operation was pretty fast, too. 7 seconds on an SSD.
– Harald
next prev parent reply other threads:[~2014-11-13 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 15:35 need help adjusting workflow to git (or vice versa) Stephen Berman
2014-11-13 15:49 ` Kelvin White
2014-11-13 19:50 ` Stephen Berman
2014-11-13 20:53 ` Kelvin White
2014-11-13 16:29 ` martin rudalics
2014-11-13 16:43 ` Andreas Schwab
2014-11-13 19:51 ` Stephen Berman
2014-11-13 20:10 ` Paul Eggert
2014-11-13 20:44 ` Stephen Berman
2014-11-13 20:58 ` Paul Eggert
2014-11-13 21:19 ` Stephen Berman
2014-11-13 20:58 ` Harald Hanche-Olsen [this message]
2014-11-13 21:22 ` Stefan Monnier
2014-11-14 5:26 ` Eli Zaretskii
2014-11-15 22:24 ` Stephen Berman
2014-11-16 18:57 ` Bill Wohler
2014-11-14 5:18 ` Rob Browning
2014-11-18 9:34 ` Eric S Fraga
2014-11-15 5:08 ` Bill Wohler
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=20141113.215827.2302048163561451721.hanche@math.ntnu.no \
--to=hanche@math.ntnu.no \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).