{"thread":{"id":"233","subject":"Re: ia64 git pull","startedAt":"2005-04-21T22:58:57Z","lastAt":"2005-04-22T03:30:18Z","messageCount":4,"participants":["Petr Baudis","Inaky Perez-Gonzalez","David A. Wheeler"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"1212","messageId":"20050421225857.GB1474@pasky.ji.cz","threadId":"233","inReplyTo":"Pine.LNX.4.58.0504211520250.2344@ppc970.osdl.org","subject":"Re: ia64 git pull","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-21T22:58:57Z","receivedAt":"2005-04-21T22:58:57Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Fri, Apr 22, 2005 at 12:29:07AM CEST, I got a letter\nwhere Linus Torvalds told me that...\n> On Thu, 21 Apr 2005 tony.luck@intel.com wrote:\n> > \n> > I can't quite see how to manage multiple \"heads\" in git. I notice that in\n> > your tree on kernel.org that .git/HEAD is a symlink to heads/master ...\n> > perhaps that is a clue.\n> \n> It's mainly a clue to bad practice, in my opinion. I personally like the \n> \"one repository, one head\" approach, and if you want multiple heads you \n> just do multiple repositories (and you can then mix just the object \n> database - set your SHA1_FILE_DIRECTORY environment variable to point to \n> the shared object database, and you're good to go). \n\nThere are two points regarding this:\n\n(i) You need to track heads of remote branches anyway.\n\n(ii) I want an easy way for user to refer to head of another working\ntree on the same repository (so that you can do just git merge testing).\n\nThis is why the multiple heads are there, and it's actually everything\nthey _do_. There's nothing more behind it.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1229","messageId":"20050422015340.GD7443@pasky.ji.cz","threadId":"233","inReplyTo":"17000.22515.170455.192374@sodium.jf.intel.com","subject":"Re: ia64 git pull","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-22T01:53:40Z","receivedAt":"2005-04-22T01:53:40Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Fri, Apr 22, 2005 at 03:48:35AM CEST, I got a letter\nwhere Inaky Perez-Gonzalez told me that...\n> >>>>> Petr Baudis writes:\n> \n> > I've just added to git-pasky a possibility to refer to branches\n> > inside of repositories by a fragment identifier:\n> \n> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#testing\n> \n> > will refer to your testing branch in that repository.\n> \n> Can we use something other than #? we'll have to scape it all the time\n> in the shell (or at least also allow some other char, something\n> without special meta-character meaning in the shell, like %).\n\nRemember that it's an URL (so you can't use '%'), and '#' is the\ncanonical URL fragment identifier delimiter. (And fragments are perfect\nfor this kind of thing, if you look at the RFC, BTW.)\n\nStill, why would you escape it? My shell will not take # as a comment\nstart if it is immediately after an alphanumeric character.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1231","messageId":"17000.23588.462823.574142@sodium.jf.intel.com","threadId":"233","inReplyTo":"20050422015340.GD7443@pasky.ji.cz","subject":"Re: ia64 git pull","fromName":"Inaky Perez-Gonzalez","fromEmail":"inaky@linux.intel.com","sentAt":"2005-04-22T02:06:28Z","receivedAt":"2005-04-22T02:06:28Z","isPatch":false,"sender":{"key":"inaky@linux.intel.com","avatar":null},"body":">>>>> Petr Baudis writes:\n\n> Remember that it's an URL (so you can't use '%'), and '#' is the\n> canonical URL fragment identifier delimiter. (And fragments are\n> perfect for this kind of thing, if you look at the RFC, BTW.)\n\nOuch, true--rule out %...\n\n> Still, why would you escape it? My shell will not take # as a\n> comment start if it is immediately after an alphanumeric character.\n\nWell, you just taught me something about bash I didn't know....\n\n/me goes back to his hole with some more knowledge.\n\nThanks,\n\n-- \n\nInaky\n\n"},{"id":"1236","messageId":"42686FCA.2010605@dwheeler.com","threadId":"233","inReplyTo":"17000.23588.462823.574142@sodium.jf.intel.com","subject":"Re: ia64 git pull","fromName":"David A. Wheeler","fromEmail":"dwheeler@dwheeler.com","sentAt":"2005-04-22T03:30:18Z","receivedAt":"2005-04-22T03:30:18Z","isPatch":false,"sender":{"key":"dwheeler@dwheeler.com","avatar":"https://avatars.githubusercontent.com/u/813150?v=4"},"body":"Petr Baudis writes:\n>>Still, why would you escape it? My shell will not take # as a\n>>comment start if it is immediately after an alphanumeric character.\n\nI guess there MIGHT be some command shell implementation\nthat stupidly _DID_ accept \"#\" as a comment character,\neven immediately after an alphanumeric.\nIf that's true, then using # there would be a pain for portability.\n\nBut I think that's highly improbable. A quick peek\nat the Single Unix Specification as posted by the Open Group\nseems to say that, according to the standards, that's NOT okay:\nhttp://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02\nBasically, the command shell is supposed to tokenize, and \"#\"\nonly means comment if it's at the beginning of a token.\n\nAnd as far as I can tell, it's not an issue in practice either.\nI did a few quick tests on Fedora Core 3 and OpenBSD.\nOn Fedora Core 3, I can say that bash, ash & csh all do NOT\nconsider \"#\" as a comment start if an alpha precedes it.\nThe same is true for OpenBSD /bin/sh, /bin/csh, and /bin/rksh.\nIf such different shells do the same thing (this stuff isn't even\nlegal C-shell text!), it's likely others do too.\n\n--- David A. Wheeler\n"}]}