emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Rainer Stengele <rainer.stengele@online.de>
Cc: emacs-orgmode@gnu.org, nicholas.dokos@hp.com
Subject: Re: Orgmode performance problem and "solution"
Date: Wed, 26 Oct 2011 10:20:20 -0400	[thread overview]
Message-ID: <4928.1319638820@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Rainer Stengele <rainer.stengele@online.de> of "Wed, 26 Oct 2011 14:16:18 +0200." <4EA7FA12.5090208@online.de>

Rainer Stengele <rainer.stengele@online.de> wrote:

> No, the old repo
> git://repo.or.cz/org-mode.git
> I used is some time behind the one I use now.
> If I want to get a fix immediately I learned I have to use the new repo git://orgmode.org/org-mode.git
> I hope I got this right.
> Rainer
> Am 26.10.2011 14:11, schrieb suvayu ali:
> > On Wed, Oct 26, 2011 at 10:07, Rainer Stengele
> > <rainer.stengele@online.de> wrote:
> >> Lacking knowledge of git I deleted everything, cloned from the new repo and compiled the files.
> >> Result was a significantly faster Org experience.
> >>
> > For future reference, a sinple `git pull` would have sufficed.
> >

It's too late for it now, but for future reference: you can change the
repo with ``git config --replace-all remote.origin.url
git://orgmode.org/org-mode.git'' and then do a ``git pull''. AFAIK, the
repo.or.cz/org-mode.git repo was a delayed mirror, so it would have the
same history (up to the point of the latest sync).

But it doesn't really matter: cloning the repo again takes longer but
it's a one-time cost and the end result is the same.


  parent reply	other threads:[~2011-10-26 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26  8:07 Orgmode performance problem and "solution" Rainer Stengele
2011-10-26  8:47 ` Jambunathan K
2011-10-26 12:11 ` suvayu ali
2011-10-26 12:16   ` Rainer Stengele
2011-10-26 12:30     ` suvayu ali
2011-10-26 14:20     ` Nick Dokos [this message]
2011-10-26 15:31   ` Dave Abrahams
2011-10-26 20:31     ` Matthew Sauer

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=4928.1319638820@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rainer.stengele@online.de \


* 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


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).