{"thread":{"id":"15485","subject":"What's in git.git (Sep 2008, #02; Wed, 10)","startedAt":"2008-09-11T03:49:40Z","lastAt":"2008-09-11T22:02:19Z","messageCount":3,"participants":["Junio C Hamano","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"90408","messageId":"7viqt3tk8b.fsf@gitster.siamese.dyndns.org","threadId":"15485","inReplyTo":null,"subject":"What's in git.git (Sep 2008, #02; Wed, 10)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-09-11T03:49:40Z","receivedAt":"2008-09-11T03:49:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"There are still a few topics that are meant for 'maint' cooking in higher\nstages; we will have 1.6.0.2 after they are merged down.\n\nOn the 'master' front, it looks like 1.6.1 will not have anything\nparticularly big like 1.6.0 did.  Other than many s/git-foo/git foo/\nupdates in tests (finished -- the documentation needs to go through the\nsame process), there are many small bells and whistles enhancements, but\nnothing earth shattering.  I am expecting that we will go into 1.6.1-rc0\nfreeze in two weeks.\n\n* The 'maint' branch has these fixes since the last announcement.\n\nArjen Laarhoven (1):\n  Use compatibility regex library for OSX/Darwin\n\nJunio C Hamano (4):\n  checkout: do not check out unmerged higher stages randomly\n  diff: Help \"less\" hide ^M from the output\n  log --author/--committer: really match only with name part\n  Update draft release notes for 1.6.0.2\n\nMarcus Griep (2):\n  Git.pm: Use File::Temp->tempfile instead of ->new\n  git-svn: Fixes my() parameter list syntax error in pre-5.8 Perl\n\nMiklos Vajna (1):\n  t7501: always use test_cmp instead of diff\n\nNicolas Pitre (5):\n  pack-objects: improve returned information from write_one()\n  improve reliability of fixup_pack_header_footer()\n  pack-objects: use fixup_pack_header_footer()'s validation mode\n  index-pack: use fixup_pack_header_footer()'s validation mode\n  fixup_pack_header_footer(): use nicely aligned buffer sizes\n\n\n* The 'master' branch has these since the last announcement\n  in addition to the above.\n\nAlex Riesen (1):\n  Add help.autocorrect to enable/disable autocorrecting\n\nAndreas Ericsson (1):\n  Teach \"git diff -p\" to locate PHP class methods\n\nArjen Laarhoven (1):\n  t6023-merge-file: Work around non-portable sed usage\n\nChristian Couder (1):\n  refs: improve comments about \"reading\" argument of \"resolve_ref\"\n\nDotan Barak (1):\n  Use xmalloc() and friends to catch allocation failures\n\nEric Wong (1):\n  git-svn: fix handling of even funkier branch names\n\nGiovanni Funchal (1):\n  configure: auto detect dynamic library path switches\n\nHeikki Orsila (1):\n  Start conforming code to \"git subcmd\" style part 2\n\nJohannes Schindelin (1):\n  git wrapper: DWIM mistyped commands\n\nJohannes Sixt (1):\n  Windows: git-shell can be compiled again\n\nJunio C Hamano (2):\n  Makefile: Allow CC_LD_DYNPATH to be overriden\n  Fix git-diff-tree --stdin\n\nMichael J Gruber (2):\n  allow installation of man and html doc from the man and html branches\n  separate build targets for man and html documentation\n\nMikael Magnusson (1):\n  Correct output of git-count-objects.\n\nNanako Shiraishi (8):\n  t/t91XX-svn: start removing use of \"git-\" from these tests\n  t/t91XX git-svn tests: run \"git svn\" not \"git-svn\"\n  t9200: use \"git cvsexportcommit\" without dash\n  t9300, t9301: use \"git fast-import/fast-export\" without dash\n  t9700: use \"git config\" without dash\n  tests: use \"git foo\" without dash in strings\n  t9101: use \"git hash-object\" without dash\n  Install git-cvsserver in $(bindir)\n"},{"id":"90429","messageId":"48C8E061.5030904@fastmail.fm","threadId":"15485","inReplyTo":"7viqt3tk8b.fsf@gitster.siamese.dyndns.org","subject":"Re: What's in git.git (Sep 2008, #02; Wed, 10)","fromName":"Michael J Gruber","fromEmail":"michaeljgruber+gmane@fastmail.fm","sentAt":"2008-09-11T09:09:53Z","receivedAt":"2008-09-11T09:09:53Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Junio C Hamano venit, vidit, dixit 11.09.2008 05:49:\n> There are still a few topics that are meant for 'maint' cooking in higher\n> stages; we will have 1.6.0.2 after they are merged down.\n> \n> On the 'master' front, it looks like 1.6.1 will not have anything\n> particularly big like 1.6.0 did.  Other than many s/git-foo/git foo/\n> updates in tests (finished -- the documentation needs to go through the\n> same process), there are many small bells and whistles enhancements, but\n\nWas there some final consensus on how to undashify the man pages? There\nis still the issue of keeping man viewers working which detect links\nfrom man page text like git-commit(1). Within a man page context forms\nlike that are natural and should not be confusing (assuming man users\nknow man), but for the html version it's unnatural. In fact, even the\nsection numbers look unnatural on the html version (pretending to be a\nnon-man-unaware html \"customer\"); also, the html doc is not split into\nsubdirs by section.\n\nI think the cleanest approach would consist in introducing another\nlinkgit macro (for everything linkgit:git-) which ouputs dashed resp.\ndashless forms for docbook (i.e. man) resp. html targets. I'll cook up a\nPOC if noone keeps me from doing so ;)\n\nMichael\n\nP.S.: There are also dashes to be removed in the text (non-link) of the\ndoc, of course. But this doesn't pose any technical hurdles.\n"},{"id":"90485","messageId":"7v8wtys5n8.fsf@gitster.siamese.dyndns.org","threadId":"15485","inReplyTo":"48C8E061.5030904@fastmail.fm","subject":"Re: What's in git.git (Sep 2008, #02; Wed, 10)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-09-11T22:02:19Z","receivedAt":"2008-09-11T22:02:19Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Michael J Gruber <michaeljgruber+gmane@fastmail.fm> writes:\n\n> I think the cleanest approach would consist in introducing another\n> linkgit macro (for everything linkgit:git-) which ouputs dashed resp.\n> dashless forms for docbook (i.e. man) resp. html targets. I'll cook up a\n> POC if noone keeps me from doing so ;)\n\nI personally think the links are Ok to be left as they are in git-foo form\nbut if there is a good way to persuade manual viewers to display \"git foo\"\nand still follow \"man git-foo\", that would be great.\n\nNames of the programs in \"git-foo\" form in the plain text, unless they are\nthe server side programs, should be updated to say \"git foo\"\n(cf. http://thread.gmane.org/gmane.comp.version-control.git/95436/focus=95443)\n"}]}