emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
Cc: Dumitru Sipos <dumitru.sipos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: basic git
Date: Fri, 30 Jun 2023 11:58:05 +0000	[thread overview]
Message-ID: <878rc1qi0i.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8v=hyi9cVMJyGv-wEQoGAzx67QhMvkxEVRnSvkcnneEWw@mail.gmail.com>

Samuel Wales <samologist@gmail.com> writes:

> apropos of nothing, btw what does one do to make org these days?
>
> make cleanall;make?  make oldorg?

Just make will trigger compilation.
make oldorg will also trigger building Info manual (in addition to compilation).
make cleanall is good to do to avoid Emacs re-using stale .elc files.


> as for other repos [i keep multiple copies for speed in switching for
> testing] to clean up an old org with a local.mk do i just delete that
> file?  can i keep doing make oldorg?

local.mk may need to be cleaned. Ideally, you just keep your specific
customizations there. Then, you do not need to clean it.

(I guess that the need to clean local.mk must not be necessary. But Org
does not do a great job defining some of the makefile settings)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-06-30 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJcAo8tvmam1dErGcM+Dv=+9=YD69XT64epb+NmYuQWFd7ZFRw@mail.gmail.com>
2023-06-30  6:55 ` basic git Samuel Wales
2023-06-30  6:56   ` Samuel Wales
2023-06-30  7:07     ` Dumitru Sipos
2023-06-30  7:20       ` Samuel Wales
2023-06-30 11:58         ` Ihor Radchenko [this message]
2023-06-30 10:14   ` Max Nikulin
2023-06-30 22:15     ` Samuel Wales
2023-07-02  3:25       ` Max Nikulin

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=878rc1qi0i.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dumitru.sipos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    /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/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).