emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bernt Hansen <bernt@norang.ca>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Testing master branch
Date: Sun, 29 Apr 2018 18:24:16 -0400	[thread overview]
Message-ID: <87sh7dfy7j.fsf@norang.ca> (raw)
In-Reply-To: <87po2iweev.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 29 Apr 2018 11:27:36 +0200")

Achim Gratz <Stromeko@nexgo.de> writes:

> Bernt Hansen writes:
>> I intend to update and track the master branch git repo changes daily in
>> order to identify problems as early as possible.
>>
>> Does it matter if I compile or not for this?
>>
>> Normally I do:
>>
>>     git pull
>>     make
>>     and restart emacs every morning
>>
>> Can I do make uncompiled instead and skip the restart?
>
> I fail to see how the two are related, unless you are talking about
> compiling a new Emacs every morning.

Hi Achim,

I use a pre-canned Emacs for windows at work so I am not ever compiling
emacs -- only the org-mode elisp code using the org-mode makefile after
updating with the latest changes.

I haven't been tracking the development branch of org-mode in about 3
years so I completely forgot about the org-reload function!  Using
org-reload is what I meant by 'restart'.  I had been restarting emacs to
use the latest compiled version of org-mode since starting to track the
master branch a week or two ago when I upgraded from version 8.3.

>
>> What do you recommend?
>
> make up2
>
> Then re-load org in your running Emacs session or restart Emacs as you
> wish.  Note that the up2 target does not install anything if any of the
> tests failed.  If you want to live dangerously, skip the tests and
> install whatever you've got, use the update2 target.

Living dangerously with my live org files at work doesn't sound like a
smart thing to do at this point :)

I'll try make-up2 and org-reload.

Thanks!
Bernt

next prev parent reply	other threads:[~2018-04-29 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29  9:08 Testing master branch Bernt Hansen
2018-04-29  9:27 ` Achim Gratz
2018-04-29 22:24   ` Bernt Hansen [this message]
2018-04-29 10:11 ` Marco Wahl
2018-04-29 22:33   ` Bernt Hansen
2018-04-29 23:39     ` Samuel Wales

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87sh7dfy7j.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).