{"thread":{"id":"7395","subject":"git.git: topics and things like that","startedAt":"2007-03-25T20:37:43Z","lastAt":"2007-03-25T23:36:16Z","messageCount":11,"participants":["Xavier Maillard","Shawn O. Pearce","Junio C Hamano","Steven Grimm","Martin Langhoff","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"37949","messageId":"200703252037.l2PKbhx6032045@localhost.localdomain","threadId":"7395","inReplyTo":null,"subject":"git.git: topics and things like that","fromName":"Xavier Maillard","fromEmail":"zedek@gnu.org","sentAt":"2007-03-25T20:37:43Z","receivedAt":"2007-03-25T20:37:43Z","isPatch":false,"sender":{"key":"zedek@gnu.org","avatar":null},"body":"Hi,\n\nThis may appear as a stupid question but as I can not find\nanything about this, I am just asking.\n\nSo, how is git development organised ? I saw there are topics but\nI do not know how patches are applied mainline (onto tip of\nmaster).\n\nWould you mind explaining this very quickly so I can understand\nmessages \"What's new in git.git\" ? :)\n\nThank you very much and sorry to bother with this basic question.\n\nXavier\n"},{"id":"37951","messageId":"20070325205226.GD12376@spearce.org","threadId":"7395","inReplyTo":"200703252037.l2PKbhx6032045@localhost.localdomain","subject":"Re: git.git: topics and things like that","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-03-25T20:52:26Z","receivedAt":"2007-03-25T20:52:26Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Xavier Maillard <zedek@gnu.org> wrote:\n> This may appear as a stupid question but as I can not find\n> anything about this, I am just asking.\n> \n> So, how is git development organised ? I saw there are topics but\n> I do not know how patches are applied mainline (onto tip of\n> master).\n\nJunio covered this well in the past.  The text has been copied into\nthe wiki:\n\n  http://git.or.cz/gitwiki/Notes\n\nBut I have to admit, it took me a while to find it.  ;-)\n \n-- \nShawn.\n"},{"id":"37954","messageId":"7vslbt2g0p.fsf@assigned-by-dhcp.cox.net","threadId":"7395","inReplyTo":"200703252037.l2PKbhx6032045@localhost.localdomain","subject":"Re: git.git: topics and things like that","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-25T21:02:30Z","receivedAt":"2007-03-25T21:02:30Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Xavier Maillard <zedek@gnu.org> writes:\n\n> So, how is git development organised ? I saw there are topics but\n> I do not know how patches are applied mainline (onto tip of\n> master).\n\nYour maintainer posts \"A note from the maintainer\" to the list\nevery once in a while describing this exact issue.\n\nThe last such message was on Feb 16th\n\n\tMessage-ID: <7vire120qc.fsf@assigned-by-dhcp.cox.net>\n\ngmane has it as article 39954:\n\n\thttp://article.gmane.org/gmane.comp.version-control.git/39954\n"},{"id":"37958","messageId":"200703252117.l2PLHFkl000601@localhost.localdomain","threadId":"7395","inReplyTo":"7vslbt2g0p.fsf@assigned-by-dhcp.cox.net","subject":"Re: git.git: topics and things like that","fromName":"Xavier Maillard","fromEmail":"zedek@gnu.org","sentAt":"2007-03-25T21:17:15Z","receivedAt":"2007-03-25T21:17:15Z","isPatch":false,"sender":{"key":"zedek@gnu.org","avatar":null},"body":"Hi,\n\n   > So, how is git development organised ? I saw there are topics but\n   > I do not know how patches are applied mainline (onto tip of\n   > master).\n\n   Your maintainer posts \"A note from the maintainer\" to the list\n   every once in a while describing this exact issue.\n\nI never have seen such message but I will read it now.\n\nAnyway, thank you.\n\nXavier\n"},{"id":"37959","messageId":"200703252117.l2PLHePA000608@localhost.localdomain","threadId":"7395","inReplyTo":"20070325205226.GD12376@spearce.org","subject":"Re: git.git: topics and things like that","fromName":"Xavier Maillard","fromEmail":"zedek@gnu.org","sentAt":"2007-03-25T21:17:40Z","receivedAt":"2007-03-25T21:17:40Z","isPatch":false,"sender":{"key":"zedek@gnu.org","avatar":null},"body":"\n   Junio covered this well in the past.  The text has been copied into\n   the wiki:\n\n     http://git.or.cz/gitwiki/Notes\n\n   But I have to admit, it took me a while to find it.  ;-)\n\nThank you very much. I will copy/paste it locally.\n\nXavier\n"},{"id":"37963","messageId":"7vhcs92cuu.fsf@assigned-by-dhcp.cox.net","threadId":"7395","inReplyTo":"200703252117.l2PLHFkl000601@localhost.localdomain","subject":"Re: git.git: topics and things like that","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-25T22:10:49Z","receivedAt":"2007-03-25T22:10:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Xavier Maillard <zedek@gnu.org> writes:\n\n>    Your maintainer posts \"A note from the maintainer\" to the list\n>    every once in a while describing this exact issue.\n>\n> I never have seen such message but I will read it now.\n\nHeh, how new are you to the list?\n\nIs every three months not often enough?  Meaning, is expecting\nnew users to look back that much backlog in the list archive too\nmuch to ask?\n"},{"id":"37966","messageId":"4606FBB6.2040902@midwinter.com","threadId":"7395","inReplyTo":"7vhcs92cuu.fsf@assigned-by-dhcp.cox.net","subject":"Re: git.git: topics and things like that","fromName":"Steven Grimm","fromEmail":"koreth@midwinter.com","sentAt":"2007-03-25T22:46:14Z","receivedAt":"2007-03-25T22:46:14Z","isPatch":false,"sender":{"key":"koreth@midwinter.com","avatar":"https://gravatar.com/avatar/71b4d2e8b62f168bdc9e9205341159e3567003b4f9e2127c617c5fa0a1f5bad2?d=mp&s=160"},"body":"Junio C Hamano wrote:\n> Heh, how new are you to the list?\n>\n> Is every three months not often enough?  Meaning, is expecting\n> new users to look back that much backlog in the list archive too\n> much to ask?\n>   \n\nI went looking for an answer to the \"what does 'pu' mean?\" question when \nI first joined the list, failed to find one, then stumbled across it by \naccident while randomly skimming the archives. \"A message from the \nmaintainer\" is not at first glance an obvious subject line to click on \nif you're searching for that kind of introductory information -- putting \non my \"unfamiliar with the list's conventions\" hat, I'd expect a message \nof that title to contain something like, \"Hey guys, can you help test \nXYZ?\" or \"The list archives will be moving in two weeks\" or, more \nlikely, \"Our hosting is costing us too much and we need donations.\"\n\nIt would be convenient for new users and, I assume, not much additional \neffort to put the URL of that Wiki page at the top of the \"what's \ncooking\" messages. Barring that, maybe the \"A message from the \nmaintainer\" email should be titled \"Introduction to git project \nmanagement\" or something similar that would make it immediately obvious \nto a new user that it's something they should read to get general \nbackground information about the project.\n\nJust IMO. At this point I've been lurking here long enough that I don't \nneed it for myself, but I do remember wishing that info were easier to find.\n\n-Steve\n"},{"id":"37967","messageId":"46a038f90703251604o21b2f805gfb280b76560de1e8@mail.gmail.com","threadId":"7395","inReplyTo":"7vhcs92cuu.fsf@assigned-by-dhcp.cox.net","subject":"Re: git.git: topics and things like that","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2007-03-25T23:04:48Z","receivedAt":"2007-03-25T23:04:48Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 3/26/07, Junio C Hamano <junkio@cox.net> wrote:\n> Heh, how new are you to the list?\n>\n> Is every three months not often enough?  Meaning, is expecting\n> new users to look back that much backlog in the list archive too\n> much to ask?\n\nI'd say he probably didn't know. Maybe an extra paragraph at the end\nof the  README  ? along the lines of ...\n\nThe project maintainer sends out regular emails to the list titled \"A\nnote from the maintainer\", \"What's cooking in git.git\" and \"Unresolved\nissues\". These messages and the discussion following them are a good\nreference for project status, development direction and bugfixing\ntasks.\n\n\ncheers,\n\n\nmartin\n"},{"id":"37968","messageId":"7v1wjc3oh7.fsf@assigned-by-dhcp.cox.net","threadId":"7395","inReplyTo":"4606FBB6.2040902@midwinter.com","subject":"Re: git.git: topics and things like that","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-25T23:14:28Z","receivedAt":"2007-03-25T23:14:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Steven Grimm <koreth@midwinter.com> writes:\n\n> ... maybe the \"A message from the\n> maintainer\" email should be titled \"Introduction to git project\n> management\" or something similar that would make it immediately\n> obvious to a new user that it's something they should read to get\n> general background information about the project.\n\nI do not necessarily think that is a better title.  It not just\ntalks the project management, but a note from the maintainer in\ngeneral.  In the future it might talk about even more things.\n\nModerated newsgroups tend to have \"foo.bar.baz FAQ\" periodical\npostings, but I'd rather not make me the authoritative FAQ\nmaintainer, as git is about distributed development and\nborrowing the convention from heavily-centralized moderated\nworld feels wrong.  Besides, it is something that does not have\nto be done by me.\n\nI just expected people to pay attention to what the maintainer\nhas to say (in addition to what the well known list regulars\nhave to say), if they wanted to know what the project is about,\nand \"A note from the maintainer\" (the message _always_ had that\ntitle) would be a good enough title for finding that.\n\nAny volunteers to maintain FAQ for the list?\n"},{"id":"37969","messageId":"7vwt1429he.fsf@assigned-by-dhcp.cox.net","threadId":"7395","inReplyTo":"46a038f90703251604o21b2f805gfb280b76560de1e8@mail.gmail.com","subject":"Re: git.git: topics and things like that","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-03-25T23:23:41Z","receivedAt":"2007-03-25T23:23:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Martin Langhoff\" <martin.langhoff@gmail.com> writes:\n\n> I'd say he probably didn't know. Maybe an extra paragraph at the end\n> of the  README  ? along the lines of ...\n>\n> The project maintainer sends out regular emails to the list titled \"A\n> note from the maintainer\", \"What's cooking in git.git\" and \"Unresolved\n> issues\". These messages and the discussion following them are a good\n> reference for project status, development direction and bugfixing\n> tasks.\n\nThanks; that is a wonderful, constructive suggestion.  Would\nhave been even better if it was presented in a patch form ;-).\n"},{"id":"37975","messageId":"eu711c$38c$2@sea.gmane.org","threadId":"7395","inReplyTo":"46a038f90703251604o21b2f805gfb280b76560de1e8@mail.gmail.com","subject":"Re: git.git: topics and things like that","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-03-25T23:36:16Z","receivedAt":"2007-03-25T23:36:16Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Martin Langhoff wrote:\n\n> On 3/26/07, Junio C Hamano <junkio@cox.net> wrote:\n>> Heh, how new are you to the list?\n>>\n>> Is every three months not often enough?  Meaning, is expecting\n>> new users to look back that much backlog in the list archive too\n>> much to ask?\n> \n> I'd say he probably didn't know. Maybe an extra paragraph at the end\n> of the  README  ? along the lines of ...\n> \n> The project maintainer sends out regular emails to the list titled \"A\n> note from the maintainer\", \"What's cooking in git.git\" and \"Unresolved\n> issues\". These messages and the discussion following them are a good\n> reference for project status, development direction and bugfixing\n> tasks.\n\nAdd \"What's in git.git (stable)\" to that.\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}