{"thread":{"id":"2900","subject":"[ANNOUNCE] GIT 1.0.0b quickfix","startedAt":"2005-12-21T22:34:11Z","lastAt":"2005-12-29T23:14:04Z","messageCount":14,"participants":["Junio C Hamano","H. Peter Anvin","Benjamin Herrenschmidt","Linus Torvalds","Ingo Oeser","Andreas Ericsson","Krzysztof Halasa"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"13897","messageId":"7vpsnq3wrg.fsf@assigned-by-dhcp.cox.net","threadId":"2900","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-21T22:34:11Z","receivedAt":"2005-12-21T22:34:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I've pushed out a v1.0.0b maint release to fix a bug in HTTP\nfetch that was discovered today X-<.\n"},{"id":"13901","messageId":"43A9E15F.1060808@zytor.com","threadId":"2900","inReplyTo":"7vpsnq3wrg.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-12-21T23:12:31Z","receivedAt":"2005-12-21T23:12:31Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Junio C Hamano wrote:\n> I've pushed out a v1.0.0b maint release to fix a bug in HTTP\n> fetch that was discovered today X-<.\n> \n\nWouldn't it make more sense for the maintenance release to be 1.0.1?\n\n\t-hpa\n"},{"id":"13905","messageId":"7vpsnqyqji.fsf@assigned-by-dhcp.cox.net","threadId":"2900","inReplyTo":"43A9E15F.1060808@zytor.com","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-21T23:32:49Z","receivedAt":"2005-12-21T23:32:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"H. Peter Anvin\" <hpa@zytor.com> writes:\n\n> Junio C Hamano wrote:\n>> I've pushed out a v1.0.0b maint release to fix a bug in HTTP\n>> fetch that was discovered today X-<.\n>>\n>\n> Wouldn't it make more sense for the maintenance release to be 1.0.1?\n\nMaybe.  Nobody mentioned this about 0.99.9a, 0.99.9b... though.\n\nThe series 1.0.0[a-z] is meant to parallel 2.6.14.[123...]\n\"fixes only\"; OTOH I'd like to allow 1.0.[123...] to contain\nenhancements.\n"},{"id":"13919","messageId":"43AA0C68.4030802@zytor.com","threadId":"2900","inReplyTo":"7vpsnqyqji.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-12-22T02:16:08Z","receivedAt":"2005-12-22T02:16:08Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Junio C Hamano wrote:\n> \"H. Peter Anvin\" <hpa@zytor.com> writes:\n> \n> \n>>Junio C Hamano wrote:\n>>\n>>>I've pushed out a v1.0.0b maint release to fix a bug in HTTP\n>>>fetch that was discovered today X-<.\n>>>\n>>\n>>Wouldn't it make more sense for the maintenance release to be 1.0.1?\n> \n> \n> Maybe.  Nobody mentioned this about 0.99.9a, 0.99.9b... though.\n\nYeah, well, the 0.99 bit in front kind of had made that hard to do.\n\n> The series 1.0.0[a-z] is meant to parallel 2.6.14.[123...]\n> \"fixes only\"; OTOH I'd like to allow 1.0.[123...] to contain\n> enhancements.\n\nWell, the Linux numbering scheme has gotten ridiculous, with the 2. in \nfront having no meaning.\n\n\t-hpa\n"},{"id":"13920","messageId":"7vu0d1u7ct.fsf@assigned-by-dhcp.cox.net","threadId":"2900","inReplyTo":"43AA0C68.4030802@zytor.com","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-22T03:40:50Z","receivedAt":"2005-12-22T03:40:50Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"H. Peter Anvin\" <hpa@zytor.com> writes:\n\n>>>Wouldn't it make more sense for the maintenance release to be 1.0.1?\n>> Maybe.  Nobody mentioned this about 0.99.9a, 0.99.9b... though.\n>\n> Yeah, well, the 0.99 bit in front kind of had made that hard to do.\n\nWell, I could have done 0.99.9.1 instead of 0.99.9a.\n\n>> The series 1.0.0[a-z] is meant to parallel 2.6.14.[123...]\n>> \"fixes only\"; OTOH I'd like to allow 1.0.[123...] to contain\n>> enhancements.\n>\n> Well, the Linux numbering scheme has gotten ridiculous, with the 2. in \n> front having no meaning.\n\nTrue.\n\nWe could do 1.0.0 (base 1.0 release), 1.0.1 (instead of 1.0.0a),\n1.0.2 (instead of 1.0.0b) on the \"maint\" branch and 1.1.0 to be\nnext minor feature release.  Do you like it better?\n"},{"id":"13921","messageId":"43AA2676.2030608@zytor.com","threadId":"2900","inReplyTo":"7vu0d1u7ct.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-12-22T04:07:18Z","receivedAt":"2005-12-22T04:07:18Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Junio C Hamano wrote:\n> \n> We could do 1.0.0 (base 1.0 release), 1.0.1 (instead of 1.0.0a),\n> 1.0.2 (instead of 1.0.0b) on the \"maint\" branch and 1.1.0 to be\n> next minor feature release.  Do you like it better?\n> \n\nI think that would make sense.\n\n\t-hpa\n"},{"id":"13925","messageId":"1135244363.10035.185.camel@gaston","threadId":"2900","inReplyTo":"43A9E15F.1060808@zytor.com","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Benjamin Herrenschmidt","fromEmail":"benh@kernel.crashing.org","sentAt":"2005-12-22T09:39:22Z","receivedAt":"2005-12-22T09:39:22Z","isPatch":false,"sender":{"key":"benh@kernel.crashing.org","avatar":null},"body":"On Wed, 2005-12-21 at 15:12 -0800, H. Peter Anvin wrote:\n> Junio C Hamano wrote:\n> > I've pushed out a v1.0.0b maint release to fix a bug in HTTP\n> > fetch that was discovered today X-<.\n> > \n> \n> Wouldn't it make more sense for the maintenance release to be 1.0.1?\n\nSeconded. letters in versions are bad. With my MacOS background, for me,\n\"b\" means \"beta\" :)\n\nBen.\n"},{"id":"13947","messageId":"Pine.LNX.4.64.0512220945450.4827@g5.osdl.org","threadId":"2900","inReplyTo":"1135244363.10035.185.camel@gaston","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-12-22T17:46:29Z","receivedAt":"2005-12-22T17:46:29Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 22 Dec 2005, Benjamin Herrenschmidt wrote:\n> > \n> > Wouldn't it make more sense for the maintenance release to be 1.0.1?\n> \n> Seconded. letters in versions are bad. With my MacOS background, for me,\n> \"b\" means \"beta\" :)\n\nFWIW, thirded. The kernel used to use letters too, and it's cute, but just \nusing multiple levels of release numbers is much more common.\n\n\t\tLinus\n"},{"id":"13951","messageId":"7vk6dxlyxl.fsf@assigned-by-dhcp.cox.net","threadId":"2900","inReplyTo":"Pine.LNX.4.64.0512220945450.4827@g5.osdl.org","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-22T19:22:14Z","receivedAt":"2005-12-22T19:22:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Linus Torvalds <torvalds@osdl.org> writes:\n\n> On Thu, 22 Dec 2005, Benjamin Herrenschmidt wrote:\n>> > \n>> > Wouldn't it make more sense for the maintenance release to be 1.0.1?\n>> \n>> Seconded. letters in versions are bad. With my MacOS background, for me,\n>> \"b\" means \"beta\" :)\n>\n> FWIW, thirded. The kernel used to use letters too, and it's cute, but just \n> using multiple levels of release numbers is much more common.\n\nFWIW, fourthed ;-)\n\ncommit c894168631e4b7da66ed3993a4c92380d38599a8\nAuthor: Junio C Hamano <junkio@cox.net>\nDate:   Wed Dec 21 22:33:37 2005 -0800\n\n    Versioning scheme changes.\n    \n    HPA suggests it is simply silly to imitate Linux versioning\n    scheme where the leading \"2\" does not mean anything anymore, and\n    I tend to agree.\n    \n    The first feature release after 1.0.0 will be 1.1.0, and the\n    development path leading to 1.1.0 will carry 1.0.GIT as the\n    version number from now on.  Similarly, the third maintenance\n    release that follows 1.0.0 will not be 1.0.0c as planned, but\n    will be called 1.0.3.  The \"maint\" branch will merge in fixes\n    and immediately tagged, so there is no need for 1.0.2.GIT that\n    is in between 1.0.2 (aka 1.0.0b) and 1.0.3.\n    \n    Signed-off-by: Junio C Hamano <junkio@cox.net>\n"},{"id":"13983","messageId":"200512231712.40621.ioe-lkml@rameria.de","threadId":"2900","inReplyTo":"Pine.LNX.4.64.0512220945450.4827@g5.osdl.org","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Ingo Oeser","fromEmail":"ioe-lkml@rameria.de","sentAt":"2005-12-23T16:12:38Z","receivedAt":"2005-12-23T16:12:38Z","isPatch":false,"sender":{"key":"ioe-lkml@rameria.de","avatar":null},"body":"On Thursday 22 December 2005 18:46, Linus Torvalds wrote:\n> On Thu, 22 Dec 2005, Benjamin Herrenschmidt wrote:\n> > > Wouldn't it make more sense for the maintenance release to be 1.0.1?\n> > Seconded. letters in versions are bad. With my MacOS background, for me,\n> > \"b\" means \"beta\" :)\n> FWIW, thirded. The kernel used to use letters too, and it's cute, but just \n> using multiple levels of release numbers is much more common.\n\nAlso sucks because letters after numbers a read as \"units\".\n\nJust compare 5h, 3kg, 20cm, 9in, 1.3h\n\nAlso putting letters after version numbers usally gives me\na feeling that the author is not sure about what he does.\nBut this is just me, I guess\n\nI hope util-linux is going to learn all that one day :-)\n\n\nRegards\n\nIngo Oeser\n"},{"id":"13999","messageId":"7vu0cyu8vj.fsf@assigned-by-dhcp.cox.net","threadId":"2900","inReplyTo":"200512231712.40621.ioe-lkml@rameria.de","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-12-24T09:44:48Z","receivedAt":"2005-12-24T09:44:48Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ingo Oeser <ioe-lkml@rameria.de> writes:\n\n> Also sucks because letters after numbers a read as \"units\".\n>\n> Just compare 5h, 3kg, 20cm, 9in, 1.3h\n\nIf your first reaction after seeing 0.99.7a 0.99.7b 0.99.7c was\nthat they were numbers in unrelated units a b c and cannot be\ncompared with each other, you need to get your head examined ;-).\n\nI concede that it is a cute point you tried to make [*1*], but I\ndo not think your presentation was convincing enough.\n\n[Footnote]\n\n*1* Which one is the heaviest, 5h, 3kg, or 20cm?\n"},{"id":"14003","messageId":"43AD2003.3060609@op5.se","threadId":"2900","inReplyTo":"7vu0cyu8vj.fsf@assigned-by-dhcp.cox.net","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2005-12-24T10:16:35Z","receivedAt":"2005-12-24T10:16:35Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Junio C Hamano wrote:\n> \n> *1* Which one is the heaviest, 5h, 3kg, or 20cm?\n> \n\n5h, without a doubt. Because time can be broken down into infinitely \nsmall pieces and encompasses all the matter in the universe it will \nalways be heavier and larger than any measurement relating to 3 \ndimensions or less.\n\nBeware of rhetorical questions around people with hangovers in a \nphilosohopical mood. ;)\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n"},{"id":"14012","messageId":"m3lkyaptwt.fsf@defiant.localdomain","threadId":"2900","inReplyTo":"43AD2003.3060609@op5.se","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"Krzysztof Halasa","fromEmail":"khc@pm.waw.pl","sentAt":"2005-12-24T12:21:38Z","receivedAt":"2005-12-24T12:21:38Z","isPatch":false,"sender":{"key":"khc@pm.waw.pl","avatar":null},"body":"Andreas Ericsson <ae@op5.se> writes:\n\n>> *1* Which one is the heaviest, 5h, 3kg, or 20cm?\n>>\n>\n> 5h, without a doubt. Because time can be broken down into infinitely\n> small pieces\n\nThis is uncertain. If the time is quantified 5 hrs might as well contain\nmuch less quanta than 3 kg, let alone 20 cm :-)\n-- \nKrzysztof Halasa\n"},{"id":"14097","messageId":"43B46DBC.2050107@zytor.com","threadId":"2900","inReplyTo":"m3lkyaptwt.fsf@defiant.localdomain","subject":"Re: [ANNOUNCE] GIT 1.0.0b quickfix","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-12-29T23:14:04Z","receivedAt":"2005-12-29T23:14:04Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Krzysztof Halasa wrote:\n> \n> This is uncertain. If the time is quantified 5 hrs might as well contain\n> much less quanta than 3 kg, let alone 20 cm :-)\n\nYou're forgetting that if time is quantized, it's as part of a general \nquantization of space-time.  Thus, there would be as many quanta in 5 \nhrs as in 539,626,442,400,000 cm.\n\n\t-hpa\n"}]}