emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Barton <mbarton98@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org + git branches for derived files
Date: Fri, 13 Aug 2021 17:53:02 -0700	[thread overview]
Message-ID: <D8890933-A018-4E77-B153-76F732BB2DFA@gmail.com> (raw)
In-Reply-To: <87czqh5gt1.fsf@gmail.com>


You could consider using git-lfs, Large File Support. There is some setup and then you can say track *.pdf and that will tell git to track the binary file in a more efficient way. I use this mailing for csv files that I want to have a snapshot version of with the Jupyter notebook that used them. Once you are tracking the files with git-lfs, they will be tracked with the normal git commits.

I agree that the best practice is not to commit these types of files, but sometimes it is handy to. By committing the PDF files to the repo, I can use Working Copy, a git client, on my iPad to quickly reference a document. Since the iPad cannot run Emacs, I am unable to regenerate the PDF from there.


> On Aug 13, 2021, at 11:40 AM, Ken Mankoff <mankoff@gmail.com> wrote:
> 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?
> Thanks,
>  -k.

  parent reply	other threads:[~2021-08-14  0:53 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 [this message]
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

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=D8890933-A018-4E77-B153-76F732BB2DFA@gmail.com \
    --to=mbarton98@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \


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