unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Xavier Maillard <xma@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Git repository and branches ?
Date: Sun, 24 Feb 2008 03:00:08 +0100	[thread overview]
Message-ID: <200802240200.m1O208m8015417@localhost.localdomain> (raw)
In-Reply-To: <87zltsidrs.fsf@catnip.gol.com> (message from Miles Bader on Sat,  23 Feb 2008 11:53:59 +0900)


   Xavier Maillard <xma@gnu.org> writes:
   > I tested it here and it worked like a charm. The only drawback is that
   > switching from a branch to master and vice versa takes very long...

   Really?  That's very surprising.  For me it's about 5 seconds to switch
   between some emacs branches, with a cold FS cache (once stuff is in the
   filesystem cache, switching is essentially instanteous).

Maybe is has to do with the hardware then; my /home is mounted
onto a SDHC card as my current laptop does not have a valid
internal HDD.

Here are the results of consecutive git branch/git checkout:

xma@localhost> git branch                                                                                     ~/usr/src/GITed/emacs
* master
  rmail-mbox
xma@localhost> time git checkout rmail-mbox                                                                   ~/usr/src/GITed/emacs
Switched to branch "rmail-mbox"
git checkout rmail-mbox  5.97s user 1.04s system 6% cpu 1:41.16 total
xma@localhost> git branch                                                                                     ~/usr/src/GITed/emacs
  master
* rmail-mbox
xma@localhost> time git checkout master                                                                       ~/usr/src/GITed/emacs
Switched to branch "master"
git checkout master  5.16s user 0.88s system 8% cpu 1:07.25 total

As you can see, the results are really bad but I do not
switch between branch so often.
   
   Are you per-chance using windows?

Are you joking ? :) I am using a real GNU/linux system, more
precisely, it is a Slackware 12.0 GNU/linux system.

	Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org




      parent reply	other threads:[~2008-02-24  2:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  2:00 Git repository and branches ? Xavier Maillard
2008-02-21  1:48 ` Miles Bader
2008-02-21 20:37   ` Michael Olson
2008-02-21 22:29     ` Miles Bader
2008-02-22  2:00   ` Xavier Maillard
2008-02-22  3:01     ` Miles Bader
2008-02-22  9:58       ` Andreas Schwab
2008-02-23  2:00         ` Xavier Maillard
2008-02-23  8:54           ` Andreas Schwab
2008-02-24  2:00             ` Xavier Maillard
2008-02-23  2:00       ` Xavier Maillard
2008-02-23  2:53         ` Miles Bader
2008-02-24  2:00           ` Xavier Maillard
2008-02-24  2:00           ` Xavier Maillard [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=200802240200.m1O208m8015417@localhost.localdomain \
    --to=xma@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.
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).