From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <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: Fri, 14 Nov 2014 07:26:19 +0200 [thread overview]
Message-ID: <83egt6jqtg.fsf@gnu.org> (raw)
In-Reply-To: <87k32yu8yh.fsf@rosalinde.fritz.box>
> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Thu, 13 Nov 2014 21:44:22 +0100
> Cc: emacs-devel@gnu.org
>
> On Thu, 13 Nov 2014 12:10:45 -0800 Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> > On 11/13/2014 11:51 AM, Stephen Berman wrote:
> >> I would be very surprised if either of these approaches is used by most
> >> developers using git, because if so, I'd have expected them to be part
> >> of the standard toolkit and well documented.
> >
> > "git clone" is part of the standard Git toolkit, and is well documented. It's
> > what I use for your scenario, if I understand the scenario correctly. And
> > "git clone" should be fast enough; for Emacs it takes 1.3 seconds on my
> > 3-year-old desktop's hard disk.
>
> That's what Martin referred to, isn't it?
Yes.
> It takes considerably longer on my older and feebler hardware, also
> compared with `bzr update' and `bzr pull --overwrite' in a shared
> repository.
Did you "git clone" from your local repo or from the remote savannah
address? The former should be very fast.
> And the size is also not insignificant, if it means having a copy of
> the entire Emacs repository for each build (~540M).
I think if you clone locally, git uses hard links for the meta-data
(or maybe it's an optional behavior that you need to activate with
some switch, see the documentation).
> Is that really the standard procedure? If so, I guess I'll get used
> to it, but it does surprise me.
Every VCS has its downsides. Bzr had only separate branches
(co-located branches were initially implemented in the last version);
git has only co-located branches. You need to work around that.
next prev parent reply other threads:[~2014-11-14 5:26 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
2014-11-13 21:22 ` Stefan Monnier
2014-11-14 5:26 ` Eli Zaretskii [this message]
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=83egt6jqtg.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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.