{"thread":{"id":"1640","subject":"[ANNOUNCE] GIT 0.99.5","startedAt":"2005-08-25T02:38:01Z","lastAt":"2005-08-26T16:24:41Z","messageCount":5,"participants":["Junio C Hamano","Martin Langhoff","Darrin Thompson","Eric W. Biederman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7733","messageId":"7vr7ci4u7q.fsf@assigned-by-dhcp.cox.net","threadId":"1640","inReplyTo":null,"subject":"[ANNOUNCE] GIT 0.99.5","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-08-25T02:38:01Z","receivedAt":"2005-08-25T02:38:01Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I've pushed out all of what has been in the proposed updates\nbranch, along with documentation updates.\n\nMany changes all over:\n\n - pulling from packed repository.\n - cvsimport.\n - documentation coverage.\n - usability.\n - terminology clarification.\n - hooks for updates and commits.\n - updated gitk.\n - multi-head push, fetch, pull, octopus merge.\n - faster merge-base.\n - git from subdirectories.\n - build procedure cleanups.\n\nHave fun.\n\n\nWhat to expect after 0.99.5\n===========================\n\nThis is written in a form of to-do list for me, so if I say\n\"accept patch\", it means I do not currently plan to do that\nmyself.  People interested in seeing it materialize please take\na hint.\n\n\nDocumentation\n-------------\n\n* Accept patches from people who actually have done CVS\n  migration and update the cvs-migration documentation.\n  Link the documentation from the main git.txt page.\n\n* Update the SubmittingPatches document to add MUA specific\n  hints on how to disable unwanted MIME and flowed-text by\n  collecting past list postings.  Accept patches from people who\n  was hit by shiny blue bat to update the same.\n\n* Talk about using rsync just once at the beginning when\n  initializing a remote repository so that local packs do not\n  need to be expanded.  I personally do not think we need tool\n  support for this.\n\n* Update tutorial to cover shared repository style a bit more,\n  maybe with a toy project that involves two or three\n  repositories.\n\n* Update tutorial to cover setting up repository hooks to do\n  common tasks.\n\n* Get help to properly use asciidoc in tutorial.\n\n* Maybe justify and demonstrate an Octopus in the tutorial.  Add\n  it to the glossary.\n\n\nTechnical (heavier)\n-------------------\n\n* Tony Luck reported an unfortunate glitch in the 3-way merge.\n  Encourage discussions to come up with a not-so-expensive way\n  to catch the kind of ambiguities that led to his misery.\n\n\nTechnical (milder)\n------------------\n\n* When the branch head pointed by $GIT_DIR/HEAD changes while\n  the index file and working tree are looking the other way\n  (e.g. somebody pushed into your repository, or you ran \"git\n  fetch\" to update the ref your working tree is on), \"git\n  checkout\" without -f gets confused.  Figure out a good way to\n  handle this.\n\n* \"git commit -m\" should work for initial commits and perhaps\n  merge commits as well.  Warning about merge is still a good\n  thing to do, while -m is useful in scripted non-interactive\n  use, so we need to be careful.\n\n* Encourage concrete proposals to commit log message templates\n  we discussed some time ago.\n\n* Bug Ryan and work with him to update send-email easier to use.\n\n* Look at portability fixes from Jason Riedy\n\n    http://www.cs.berkeley.edu/~ejr/gits/git.git#portable \n\n* Accept patches to cause \"read-tree -u\" delete a directory when\n  it makes it empty.\n\n* Perhaps accept patches to introduce the concept of \"patch flow\n  expressed as ref mappings\" Josef has been advocating about.\n\n* MIMEified applymbox to grok B and Q encodings in headers and\n  turn them into UTF-8; unwrap QP; explode multipart.\n\n* \"git cherry-pick\" that applies the patch an existing commit\n  introduces in its ancestry chain, possibly using the 3-way\n  merge machinery; update rebase using the cherry-pick command.\n  Carl's redo/undo might fall out naturally from this.\n\n* A tool to detect, show and prune already merged topic\n  branches.\n\n* Perhaps \"git branch -d\" to delete a branch.\n\n* Enhance \"git repack\" to not always use --all; this would be\n  handy if the repository contains wagging heads like \"pu\" in\n  git.git repository.\n\n* Remove \"git clone-dumb-http\".\n"},{"id":"7737","messageId":"46a038f9050824203027fbca0@mail.gmail.com","threadId":"1640","inReplyTo":"7vr7ci4u7q.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.5","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2005-08-25T03:30:53Z","receivedAt":"2005-08-25T03:30:53Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 8/25/05, Junio C Hamano <junkio@cox.net> wrote:\n> Have fun.\n\nYay!\n\n> What to expect after 0.99.5\n> ===========================\n\n> Documentation\n> -------------\n\nPerhaps link the 'howto' docs from the git formal docs, so they are\nvisible via http://www.kernel.org/pub/software/scm/git/docs/\n\n> * Accept patches from people who actually have done CVS\n>   migration and update the cvs-migration documentation.\n>   Link the documentation from the main git.txt page.\n\nYup, run trial conversions for about half a dozen cvs repos, and\ncurrently tracking external cvs projects with git too. Will update\ndocs as I find time.\n\n> * Update tutorial to cover shared repository style a bit more,\n>   maybe with a toy project that involves two or three\n>   repositories.\n\nI recently wrote one such 'shared repo' tutorial for internal\nconsumption at work. Should clean it up, and add to the howto dir. The\nincentive here would be to see the howtos on the web - and then I can\npoint people at it directly.\n\n> Technical (milder)\n> ------------------\n\nPersonally, I want to complete the Arch import. I'm interested in\nfeedback on the current code -- anyone has an interest in migration\nfrom Arch or similar patch-centric SCM?\n\ncheers,\n\n\nmartin\n"},{"id":"7752","messageId":"1124996741.4110.8.camel@localhost.localdomain","threadId":"1640","inReplyTo":"7vr7ci4u7q.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.5","fromName":"Darrin Thompson","fromEmail":"darrint@progeny.com","sentAt":"2005-08-25T19:05:41Z","receivedAt":"2005-08-25T19:05:41Z","isPatch":false,"sender":{"key":"darrint@progeny.com","avatar":null},"body":"On Wed, 2005-08-24 at 19:38 -0700, Junio C Hamano wrote:\n> * Update tutorial to cover shared repository style a bit more,\n>   maybe with a toy project that involves two or three\n>   repositories.\n> \n\nShameless plug: Feel free to use/modify/steal my writeup:\n\nhttp://willowbend.cx/archives/2005/08/24/git-epiphany/\n\n--\nDarrin\n"},{"id":"7809","messageId":"m1y86ospej.fsf@ebiederm.dsl.xmission.com","threadId":"1640","inReplyTo":"7vr7ci4u7q.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 0.99.5","fromName":"Eric W. Biederman","fromEmail":"ebiederm@xmission.com","sentAt":"2005-08-26T15:12:36Z","receivedAt":"2005-08-26T15:12:36Z","isPatch":false,"sender":{"key":"ebiederm@xmission.com","avatar":"https://avatars.githubusercontent.com/u/7477136?v=4"},"body":"Junio C Hamano <junkio@cox.net> writes:\n\n> Documentation\n> -------------\n\n\nA nit but possibly an important for 1.0 there are\nquite a few git commands that don't have man pages\nor whose man pages are currently very poor.\n\nGetting the code sane and stable of course comes first\nbut if people can't figure out how to use git...\n\nEric\n"},{"id":"7811","messageId":"7vr7cgfyye.fsf@assigned-by-dhcp.cox.net","threadId":"1640","inReplyTo":"m1y86ospej.fsf@ebiederm.dsl.xmission.com","subject":"Re: [ANNOUNCE] GIT 0.99.5","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-08-26T16:24:41Z","receivedAt":"2005-08-26T16:24:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"ebiederm@xmission.com (Eric W. Biederman) writes:\n\n> A nit but possibly an important for 1.0 there are\n> quite a few git commands that don't have man pages\n> or whose man pages are currently very poor.\n>\n> Getting the code sane and stable of course comes first\n> but if people can't figure out how to use git...\n\nI have been worried about that since I posted my first \"last\nmile\" message.  My excuse is that there are only 24 hours in a\nday.  Patches welcome.\n"}]}