git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Using git to track my PhD thesis, couple of questions

From
Sseanh <seanh.nospam@gmail.com>
Date
Aug 28, 2009, 13:37 UTC
Message-ID
<20090828133708.GA11146@kisimul>
In-Reply-To
<vpq7hwo8gxd.fsf@bauges.imag.fr>
Wow, really helpful responses, thanks a lot.

I think having read all this that I'll do it manually. I'll still use git to track my latex source and will commit to it as often as I like and not worry about commit granularity. Whenever I've finished a significant chunk I'll add a PDF of it to a manually edited web page along with a description of what changed since the last time I added a PDF. I can use git log etc to help write the manual changelog. My supervisors can just look at this manually constructed page and if it gets too big I'll just archive the oldest PDFs. I can tag the git repo at the points where I add a PDF to the web page. I guess this is pretty close to what software projects do with version releases and their public website.

On Thu, Aug 27, 2009 at 01:41:04PM -0700, Sverre Rabbelier wrote:
> If they only care about the pdf anyway, why not have a separate branch
> to which you commit the pdf's instead?

Well I was thinking they'd look at the changelogs with the diffs showing exactly what changed in the latex source files, which should be pretty self-explanatory, but then when they wanted to read a whole chapter and add comments to it they'd want the PDF not the latex.

I don't really understand the script Junio posted (not literate in sh) 
but I think it might have something to do with copying changelogs over 
from the source repo to a PDFs repo.
 
On Fri, Aug 28, 2009 at 12:21:42AM +0200, demerphq wrote:
> As you can generate the PDF's from the latex then just hack gitweb to
> let them download it from there.

Unfortunately gitweb is written in Perl. But I know what you mean, it should in theory be possible for them to click on a 'Get PDF' link for a particular revision that causes the PDF to be built and returned to their browser.

In response to Matthieu and Paolo, I'm not sure I understand the git internals involved in the discussion around merge --squash, I had a feeling this would produce a 'merge' that git in some sense would 'not know about', since it sounds complex and I don't understand it I don't think I want to go there.

Thanks all
Previous: Matthieu MoyNext: Matthieu Moy
Message 6 of 23 in “Using git to track my PhD thesis, couple of questions”
  1. seanhAug 27, 2009
  2. Sverre RabbelierAug 27, 2009
  3. Matthieu MoyAug 27, 2009
  4. Paolo BonziniAug 28, 2009
  5. Matthieu MoyAug 28, 2009
  6. seanhAug 28, 2009
  7. Matthieu MoyAug 28, 2009
  8. Matthias AndreeAug 28, 2009
  9. Merging in Subversion 1.5 (was: Re: Using git to track my PhD thesis, couple of questions)Jakub Narebski, Aug 28, 2009
  10. Avery PennarunAug 28, 2009
  11. Matthias AndreeAug 28, 2009
  12. Jakub NarebskiAug 28, 2009
  13. Matthias AndreeAug 28, 2009
  14. Avery PennarunAug 28, 2009
  15. Sam VilainAug 30, 2009
  16. Dmitry PotapovAug 31, 2009
  17. david@lang.hmAug 28, 2009
  18. Paolo BonziniAug 28, 2009
  19. demerphqAug 28, 2009
  20. david@lang.hmAug 28, 2009
  21. demerphqAug 28, 2009
  22. Junio C HamanoAug 27, 2009
  23. demerphqAug 27, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.