all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Mark Barton <mbarton98@gmail.com>,
	Rob Sargent <robjsargent@gmail.com>,
	Tim Cross <theophilusx@gmail.com>
Subject: Re: Org + git branches for derived files
Date: Sun, 15 Aug 2021 18:02:31 -0700	[thread overview]
Message-ID: <87lf5242xk.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8sXkHqwV6WZpJ54Er1Rvj-e+iaEos5gc++teS8sOoJKzA@mail.gmail.com>

Hi All,

Thank you for the suggestions.

I think the most elegant solution is to have a hook on GitHub that compiles the PDF on a remote server. But it takes a lot more work, because I don't necessarily have *everything* in Git - my local 'library.bib' usually isn't included, nor my custom emacs config, latexmkrc, etc. 

I'd just like the compiled PDF easily readable by anyone, but I don't want 100s of historical copies.

There are a few solutions.

1) Maintain a branch with the 'no-history' files. When they need to be updated, commit and amend, then force-push. See https://stackoverflow.com/questions/22824922/git-commit-and-push-a-binary-file-but-dont-keep-history

2) Add the 'no-history' files to their own commit in the main branch. When they need to be updated, make a new commit and rebase/fixup from the previous commit. See https://stackoverflow.com/questions/12964145/how-to-config-git-to-overwrite-non-text-file-instead-of-version-controlled-it

  -k.



  reply	other threads:[~2021-08-16  1:03 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 [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=87lf5242xk.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbarton98@gmail.com \
    --cc=robjsargent@gmail.com \
    --cc=theophilusx@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.