From: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: use case: keep the output of a markup (TeX) file under revision control
Date: Fri, 18 Feb 2011 07:59:36 +0100 [thread overview]
Message-ID: <4D5E18D8.8030106@atlas-elektronik.com> (raw)
In-Reply-To: <1297972319.3944.30.camel@mattotaupa>
On 2/17/2011 8:51 PM, Paul Menzel wrote:
>> Why don't you keep the PDF files in a separate branch ? Look at git's
>> git repository (http://git.kernel.org/?p=git/git.git) in the html
>> and man branches.
>
> Very interesting. Thank you very much for this hint.
>
> Is the used solution in git’s git repository a result of the problem
> with maintaining generated output from source files or does it have
> other other advantages too?
>
> When creating TeX documents – at least in my work flow – I always have
> the PDF file open in parallel. Would that be a problem when having it in
> a separate branch?
I'd create a second clone and checkout the 'PDF' (or whatever you might call
it) branch there.
> Also I guess that this is done automatically too (saying autogenerated
> in `git log origin/man`). I could not find the script though.
>
> $ git grep Autogen
> git-gui/Makefile: echo '# Autogenerated by git-gui Makefile' >$@ && \
> git-gui/git-gui.sh:if {[gets $fd] eq {# Autogenerated by git-gui Makefile}} {
>
> and searching for »git "Autogenerated manpages for"« did not return
> anything useful for me.
Try: git grep "Autogenerated " origin/todo
It's in 'dodoc.sh' on branch 'todo'
> Additionally I am confused where the SHA id g43f9f in »Autogenerated
> manpages for v1.7.4.1-42-g43f9f« comes from. I could not find that
> commit in `origin/master` or `git log v1.7.4.1`.
Try: git show 43f9f (and 'git help describe')
> The last thing is that in git’s git repository the autogeneration of the
> manual pages does not seem to happen every commit (Is it a cron job?).
> In my use case the PDF file should be generated after every commit. Is a
> separate branch the way to go here?
I guess the autogeneration takes place on every push to 'master'. That
should work for you, too. Your decision...
HTH,
Stefan
--
----------------------------------------------------------------
/dev/random says: I was going to procrastinate, but I put it off....
next prev parent reply other threads:[~2011-02-18 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 10:37 use case: keep the output of a markup (TeX) file under revision control Paul Menzel
2011-02-17 12:03 ` Stefan Naewe
2011-02-17 19:51 ` Paul Menzel
2011-02-18 6:59 ` Stefan Naewe [this message]
2011-02-17 12:19 ` Jakub Narebski
2011-02-17 12:27 ` Stefan Naewe
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=4D5E18D8.8030106@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik.com \
--cc=git@vger.kernel.org \
--cc=paulepanter@users.sourceforge.net \
/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.
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 NNTP newsgroup(s).