I'm planning to use git to track my PhD thesis as I work on it and to
let my supervisors track it. I've setup a git repository and a gitweb
instance showing it. There are a couple of specific requirements.
1. My supervisors don't want to see all the little commits that I make
day by day. So I'll commit to a dev branch, then whenever I've made
significant progress will merge it into a trunk branch. I want the trunk
branch to get all the changes but as one big commit, not inherit all the
little commits like a normal merge would do. I think this is a `git
merge --squash`. Btw the help for that command ends quite brilliantly:
"(or more in case of an octopus)".
2. They don't want to look at the latex source but the PDFs built from
it, which they're going to annotate with their comments. So I need an
easy way for them to get the PDF of each commit from gitweb without
having to checkout the repo and build it themselves. Normally I
wouldn't commit the PDF files into the repo because they're compiled
files not source files, but it seems that just building a PDF and
committing it along with each commit to trunk would be by far the
easiest way to achieve this. But will git store the PDFs efficiently, or
will the repo start to get really big?
Thanks
Heya,
On Thu, Aug 27, 2009 at 13:34, seanh[off-list ref] wrote:
2. They don't want to look at the latex source but the PDFs built from
it, which they're going to annotate with their comments. So I need an
easy way for them to get the PDF of each commit from gitweb without
having to checkout the repo and build it themselves. Normally I
wouldn't commit the PDF files into the repo because they're compiled
files not source files, but it seems that just building a PDF and
committing it along with each commit to trunk would be by far the
easiest way to achieve this. But will git store the PDFs efficiently, or
will the repo start to get really big?
If they only care about the pdf anyway, why not have a separate branch
to which you commit the pdf's instead?
--
Cheers,
Sverre Rabbelier
2009/8/27 seanh [off-list ref]:
2. They don't want to look at the latex source but the PDFs built from
it, which they're going to annotate with their comments. So I need an
easy way for them to get the PDF of each commit from gitweb without
having to checkout the repo and build it themselves. Normally I
wouldn't commit the PDF files into the repo because they're compiled
files not source files, but it seems that just building a PDF and
committing it along with each commit to trunk would be by far the
easiest way to achieve this. But will git store the PDFs efficiently, or
will the repo start to get really big?
As you can generate the PDF's from the latex then just hack gitweb to
let them download it from there.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"