From: Timothy <tecosaur@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org + git branches for derived files
Date: Tue, 31 Aug 2021 20:21:49 +0800 [thread overview]
Message-ID: <87wno1olaq.fsf@gmail.com> (raw)
In-Reply-To: <87czqh5gt1.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Hi Ken,
It’s been a while, but just to chime in: if you use GitHub you may find
<https://github.com/marketplace/actions/org-knit> to be of use.
Let me know if you have any questions, I wrote it a few months ago.
Ken Mankoff <mankoff@gmail.com> writes:
> Hello,
>
> I think this might be more of a git question than an Org question, but I imagine I might find the answer here and that it might be useful to others, so I ask here.
>
> I’d like to keep derivative products (the LaTeX output, the final PDF, etc.)
> available in Git, but not commit those changes each time I change the Org file.
> Perhaps git-annex as appropriate for this, but seems over-kill.
>
> Is there some way to mostly-seamlessly commit the LaTeX and/or PDF and/or other
> files to their own git branches but in a way that overwrites the history of that
> branch, so that a small Org file that generates a big binary PDF does not
> pollute the git tree?
All the best,
Timothy
prev parent reply other threads:[~2021-08-31 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 18:40 Org + git branches for derived files Ken Mankoff
2021-08-13 20:53 ` Juan Manuel Macías
2021-08-13 23:10 ` Tim Cross
2021-08-14 0:53 ` Mark Barton
2021-08-14 1:53 ` Rob Sargent
2021-08-14 3:44 ` Rob Sargent
2021-08-14 4:21 ` Samuel Wales
2021-08-16 1:02 ` Ken Mankoff
2021-08-16 4:58 ` Rob Sargent
2021-08-31 12:21 ` Timothy [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wno1olaq.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).