From: Paul Eggert <eggert@cs.ucla.edu>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: need help adjusting workflow to git (or vice versa)
Date: Thu, 13 Nov 2014 12:58:24 -0800 [thread overview]
Message-ID: <54651B70.2080302@cs.ucla.edu> (raw)
In-Reply-To: <87k32yu8yh.fsf@rosalinde.fritz.box>
On 11/13/2014 12:44 PM, Stephen Berman wrote:
> 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.
By "shared repository" do you mean you have just one copy of the working
files? I thought you had multiple copies, one for each branch. That's
what I do, as it helps 'make' go faster.
> And the size is also not insignificant, if it means having a copy of
> the entire Emacs repository for each build (~540M).
No, the repository is shared:
$ time git clone master tmp
Cloning into 'tmp'...
done.
real 0m1.314s
user 0m0.997s
sys 0m0.280s
$ du -s master/.git tmp/.git
205500 master/.git
768 tmp/.git
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 [this message]
2014-11-13 21:19 ` Stephen Berman
2014-11-13 20:58 ` Harald Hanche-Olsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54651B70.2080302@cs.ucla.edu \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.