From: Rob Sargent <robjsargent@gmail.com>
To: Mark Barton <mbarton98@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>, Ken Mankoff <mankoff@gmail.com>
Subject: Re: Org + git branches for derived files
Date: Fri, 13 Aug 2021 19:53:45 -0600 [thread overview]
Message-ID: <B60D54F4-FC76-4126-B3E7-56E8F1E171C0@gmail.com> (raw)
In-Reply-To: <D8890933-A018-4E77-B153-76F732BB2DFA@gmail.com>
> On Aug 13, 2021, at 6:54 PM, Mark Barton <mbarton98@gmail.com> wrote:
>
> Ken,
>
> 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.
>
> Mark
If you’re using GitHub or gitlab you can place artifacts along side your code repo. One often sees executables and jars there. Typically built and updated by mechanisms on the holster on a “release” action or similar event
next prev parent reply other threads:[~2021-08-14 1:54 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 [this message]
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:
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=B60D54F4-FC76-4126-B3E7-56E8F1E171C0@gmail.com \
--to=robjsargent@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
--cc=mbarton98@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.