{"thread":{"id":"17287","subject":"[PATCH 1/2] user-manual: Simplify the user configuration.","startedAt":"2009-01-21T18:09:24Z","lastAt":"2009-01-25T23:20:00Z","messageCount":25,"participants":["Felipe Contreras","Markus Heidelberg","Jeff King","Junio C Hamano","Wincent Colaiuta","Hannu Koivisto","Johannes Schindelin","Kyle Moffett"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"101411","messageId":"1232561365-5919-1-git-send-email-felipe.contreras@gmail.com","threadId":"17287","inReplyTo":null,"subject":"[PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-21T18:09:24Z","receivedAt":"2009-01-21T18:09:24Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"This is shorter, avoids the burder to think about the format of the\nconfiguration file, and git config is already used in other places in\nthe manual.\n\nSigned-off-by: Felipe Contreras \n---\n Documentation/user-manual.txt | 8 +++-----\n 1 files changed, 3 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex 19f571a..3a9704c 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -981,13 +981,11 @@ Telling git your name\n ---------------------\n \n Before creating any commits, you should introduce yourself to git. The\n-easiest way to do so is to make sure the following lines appear in a\n-file named .gitconfig in your home directory:\n+easiest way is to use the linkgit:git-config[1] command:\n \n ------------------------------------------------\n-[user]\n-\tname = Your Name Comes Here\n-\temail = you@yourdomain.example.com\n+$ git config user.name \"Your Name Comes Here\"\n+$ git config user.email you@yourdomain.example.com\n ------------------------------------------------\n \n (See the \"CONFIGURATION FILE\" section of linkgit:git-config[1] for\n-- \n1.6.1\n"},{"id":"101412","messageId":"1232561365-5919-2-git-send-email-felipe.contreras@gmail.com","threadId":"17287","inReplyTo":"1232561365-5919-1-git-send-email-felipe.contreras@gmail.com","subject":"[PATCH 2/2] Fix typo.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-21T18:09:25Z","receivedAt":"2009-01-21T18:09:25Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"\"its pointless\" is wrong, should be \"it is pointless\" so \"it's\npointless\".\n\nSigned-off-by: Felipe Contreras \n---\n sha1_file.c | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/sha1_file.c b/sha1_file.c\nindex f08493f..69fef9f 100644\n--- a/sha1_file.c\n+++ b/sha1_file.c\n@@ -800,7 +800,7 @@ unsigned char* use_pack(struct packed_git *p,\n \tif (p->pack_fd == -1 && open_packed_git(p))\n \t\tdie(\"packfile %s cannot be accessed\", p->pack_name);\n \n-\t/* Since packfiles end in a hash of their content and its\n+\t/* Since packfiles end in a hash of their content and it's\n \t * pointless to ask for an offset into the middle of that\n \t * hash, and the in_window function above wouldn't match\n \t * don't allow an offset too close to the end of the file.\n-- \n1.6.1\n"},{"id":"101418","messageId":"200901211955.47362.markus.heidelberg@web.de","threadId":"17287","inReplyTo":"1232561365-5919-1-git-send-email-felipe.contreras@gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Markus Heidelberg","fromEmail":"markus.heidelberg@web.de","sentAt":"2009-01-21T18:55:47Z","receivedAt":"2009-01-21T18:55:47Z","isPatch":true,"sender":{"key":"markus.heidelberg@web.de","avatar":"https://avatars.githubusercontent.com/u/6334512?v=4"},"body":"Felipe Contreras, 21.01.2009:\n> +++ b/Documentation/user-manual.txt\n> @@ -981,13 +981,11 @@ Telling git your name\n> ---------------------\n> \n> Before creating any commits, you should introduce yourself to git. The\n> -easiest way to do so is to make sure the following lines appear in a\n> -file named .gitconfig in your home directory:\n> +easiest way is to use the linkgit:git-config[1] command:\n> \n> ------------------------------------------------\n> -[user]\n> -\tname = Your Name Comes Here\n> -\temail = you@yourdomain.example.com\n> +$ git config user.name \"Your Name Comes Here\"\n> +$ git config user.email you@yourdomain.example.com\n\n--global\n\nMarkus\n"},{"id":"101420","messageId":"1232564650-3701-1-git-send-email-felipe.contreras@gmail.com","threadId":"17287","inReplyTo":"200901211955.47362.markus.heidelberg@web.de","subject":"[PATCH] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-21T19:04:10Z","receivedAt":"2009-01-21T19:04:10Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"This is shorter, avoids the burder to think about the format of the\nconfiguration file, and git config is already used in other places in\nthe manual.\n\nSigned-off-by: Felipe Contreras \n---\n Documentation/user-manual.txt | 8 +++-----\n 1 files changed, 3 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex 19f571a..c8a1b7b 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -981,13 +981,11 @@ Telling git your name\n ---------------------\n \n Before creating any commits, you should introduce yourself to git. The\n-easiest way to do so is to make sure the following lines appear in a\n-file named .gitconfig in your home directory:\n+easiest way is to use the linkgit:git-config[1] command:\n \n ------------------------------------------------\n-[user]\n-\tname = Your Name Comes Here\n-\temail = you@yourdomain.example.com\n+$ git config --global user.name \"Your Name Comes Here\"\n+$ git config --global user.email you@yourdomain.example.com\n ------------------------------------------------\n \n (See the \"CONFIGURATION FILE\" section of linkgit:git-config[1] for\n-- \n1.6.1\n"},{"id":"101427","messageId":"20090121191808.GF21686@coredump.intra.peff.net","threadId":"17287","inReplyTo":"1232564650-3701-1-git-send-email-felipe.contreras@gmail.com","subject":"Re: [PATCH] user-manual: Simplify the user configuration.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-21T19:18:08Z","receivedAt":"2009-01-21T19:18:08Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Jan 21, 2009 at 09:04:10PM +0200, Felipe Contreras wrote:\n\n> This is shorter, avoids the burder to think about the format of the\n> configuration file, and git config is already used in other places in\n> the manual.\n\nI seem to recall this coming up several times before, and there being a\nsentiment that it was _good_ to introduce the user to concept of a\nconfig file. It lets them know that it exists, approximately what the\nsyntax looks like, and demystifies what is going on when you type \"git\nconfig\" (i.e., it intentionally shows that there is more than way to do\nit).\n\nI don't have a personal preference, but you may want to grep the\nlist archives for other discussion.\n\n-Peff\n"},{"id":"101431","messageId":"94a0d4530901211139x6296a48m14aa7ce1d8e65145@mail.gmail.com","threadId":"17287","inReplyTo":"20090121191808.GF21686@coredump.intra.peff.net","subject":"Re: [PATCH] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-21T19:39:27Z","receivedAt":"2009-01-21T19:39:27Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Wed, Jan 21, 2009 at 9:18 PM, Jeff King wrote:\n> On Wed, Jan 21, 2009 at 09:04:10PM +0200, Felipe Contreras wrote:\n>\n>> This is shorter, avoids the burder to think about the format of the\n>> configuration file, and git config is already used in other places in\n>> the manual.\n>\n> I seem to recall this coming up several times before, and there being a\n> sentiment that it was _good_ to introduce the user to concept of a\n> config file. It lets them know that it exists, approximately what the\n> syntax looks like, and demystifies what is going on when you type \"git\n> config\" (i.e., it intentionally shows that there is more than way to do\n> it).\n>\n> I don't have a personal preference, but you may want to grep the\n> list archives for other discussion.\n\nThat's over complicating the user with what should probably be one of\nthe first things to do. Besides, do Windows users know which is their\nhome directory?\n\nMaybe a comment like previous git config commands:\nIf you examine the file .gitconfig in your home directory, you will see this:\n\n------------------------------------------------\n...\n[user]\n name = Your Name Comes Here\n email = you@yourdomain.example.com\n...\n------------------------------------------------\n\n-- \nFelipe Contreras\n"},{"id":"101434","messageId":"20090121195156.GA3589@sigill.intra.peff.net","threadId":"17287","inReplyTo":"94a0d4530901211139x6296a48m14aa7ce1d8e65145@mail.gmail.com","subject":"Re: [PATCH] user-manual: Simplify the user configuration.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-21T19:51:56Z","receivedAt":"2009-01-21T19:51:56Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Jan 21, 2009 at 09:39:27PM +0200, Felipe Contreras wrote:\n\n> That's over complicating the user with what should probably be one of\n> the first things to do. Besides, do Windows users know which is their\n> home directory?\n\nLike I said, I don't care one way or the other, personally. But you\nshould at least address points brought up in the previous iterations:\n\n http://thread.gmane.org/gmane.comp.version-control.git/37921/focus=38007\n\n http://thread.gmane.org/gmane.comp.version-control.git/46903\n\n-Peff\n"},{"id":"101444","messageId":"7v8wp4e5wn.fsf@gitster.siamese.dyndns.org","threadId":"17287","inReplyTo":"1232561365-5919-1-git-send-email-felipe.contreras@gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-01-21T20:54:48Z","receivedAt":"2009-01-21T20:54:48Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Felipe Contreras writes:\n\n> This is shorter, avoids the burder to think about the format of the\n> configuration file, and git config is already used in other places in\n> the manual.\n\nI am moderately against changing this part to use \"git config\".\n\nWe traditionally introduced how to set configuration variables first by\nediting it in an editor, and this was quite deliberate, in order to show\nhow the configuration file looks like, to demonstrate that there is no\ndeep magic in the file format, and to explain that it is perfectly Ok to\nedit it without using \"git config\" command.\n\nI actually wish this section appeared a lot earlier in the document, but\nthat is a separate issue.\n"},{"id":"101450","messageId":"8C518E90-A7AE-48F0-A1A3-F333B21F468E@wincent.com","threadId":"17287","inReplyTo":"7v8wp4e5wn.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Wincent Colaiuta","fromEmail":"win@wincent.com","sentAt":"2009-01-21T21:13:10Z","receivedAt":"2009-01-21T21:13:10Z","isPatch":true,"sender":{"key":"greg@hurrell.net","avatar":"https://avatars.githubusercontent.com/u/7074?v=4"},"body":"El 21/1/2009, a las 21:54, Junio C Hamano escribió:\n\n> Felipe Contreras writes:\n>\n>> This is shorter, avoids the burder to think about the format of the\n>> configuration file, and git config is already used in other places in\n>> the manual.\n>\n> I am moderately against changing this part to use \"git config\".\n>\n> We traditionally introduced how to set configuration variables first \n> by\n> editing it in an editor, and this was quite deliberate, in order to \n> show\n> how the configuration file looks like, to demonstrate that there is no\n> deep magic in the file format, and to explain that it is perfectly \n> Ok to\n> edit it without using \"git config\" command.\n\nIf that's the goal, why not do both?:\n\n1. Show people how to use \"git config\" like this patch does (seeing as \nit's easier and less error prone)\n\n2. Tell people that they can inspect and even edit the config file by \nhand if they want\n\nThe actual order of 1 and 2 depends on where you want to place more \nemphasis:\n\nSomething like either:\n\n> Before creating any commits, you should introduce yourself to git. \n> The\n> easiest way to do so is to make sure the following lines appear in a\n> file named .gitconfig in your home directory:\n>\n> [user]\n> \tname = Your Name Comes Here\n> \temail = you@yourdomain.example.com\n>\n> As a convenience you can use linkgit:git-config[1] to modify \n> your .gitconfig\n> instead of editing it by hand:\n>\n> $ git config --global user.name \"Your Name Comes Here\"\n> $ git config --global user.email you@yourdomain.example.com\n\n\nOr:\n\n\n> Before creating any commits, you should introduce yourself to git. \n> The\n> easiest way is to use the linkgit:git-config[1] command:\n>\n> $ git config --global user.name \"Your Name Comes Here\"\n> $ git config --global user.email you@yourdomain.example.com\n>\n> Your settings are written to a file named .gitconfig in your home\n> directory which you can inspect or even edit by hand. Settings look \n> like this:\n>\n> [user]\n> \tname = Your Name Comes Here\n> \temail = you@yourdomain.example.com\n\n\nCheers,\nWincent\n"},{"id":"101452","messageId":"94a0d4530901211319t8126611wc1437848631fe988@mail.gmail.com","threadId":"17287","inReplyTo":"7v8wp4e5wn.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-21T21:19:11Z","receivedAt":"2009-01-21T21:19:11Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Wed, Jan 21, 2009 at 10:54 PM, Junio C Hamano wrote:\n> Felipe Contreras writes:\n>\n>> This is shorter, avoids the burder to think about the format of the\n>> configuration file, and git config is already used in other places in\n>> the manual.\n>\n> I am moderately against changing this part to use \"git config\".\n>\n> We traditionally introduced how to set configuration variables first by\n> editing it in an editor, and this was quite deliberate, in order to show\n> how the configuration file looks like, to demonstrate that there is no\n> deep magic in the file format, and to explain that it is perfectly Ok to\n> edit it without using \"git config\" command.\n>\n> I actually wish this section appeared a lot earlier in the document, but\n> that is a separate issue.\n\nI agree that it's good that people get familiar with the config\nformat, and that it should appear earlier in the document, perhaps as\na separate section. However, for new users that just want to get\nstarted any extra burden weighs in the misconception that git is not\nuser friendly.\n\nI read the comments in both threads Jeff pointed out and I have\ncomments regarding the argument that it's easy to edit a text file.\n\nIt's easy to *change* a text file, not so much to write something by\nhand. Although the user would probably just copy-paste the text from\nthe online manual (changing spaces by a tag in the process) there's a\npossibility that the manual is printed.\n\nThis brings back my previous question: where is the home directory in\na Windows system?\n\nAn idea would be to add an --edit option to git config, so the users\ndon't need to care about the location of the text file and just do\n\"git config --global --edit\" which would bring the editor. Although\nI'm not sure how that would work on Windows since the editor is\nprobably not properly configured at that point.\n\nNow, *nobody* has replied back the comments of providing both the git\nconfig command and .gitconfig snip. It was mentioned in both threads\nand ignored.\n\nAnyone against that?\n\n-- \nFelipe Contreras\n"},{"id":"101535","messageId":"831vuvfh7t.fsf@kalahari.s2.org","threadId":"17287","inReplyTo":"94a0d4530901211319t8126611wc1437848631fe988@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Hannu Koivisto","fromEmail":"azure@iki.fi","sentAt":"2009-01-22T16:17:26Z","receivedAt":"2009-01-22T16:17:26Z","isPatch":true,"sender":{"key":"azure@iki.fi","avatar":null},"body":"Felipe Contreras writes:\n\n> This brings back my previous question: where is the home directory in\n> a Windows system?\n\nIt's where %HOMEDRIVE%%HOMEPATH% points to.\n\n-- \nHannu\n"},{"id":"101547","messageId":"94a0d4530901220857q1027c05bs137dcc0244a1cc5a@mail.gmail.com","threadId":"17287","inReplyTo":"831vuvfh7t.fsf@kalahari.s2.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-22T16:57:23Z","receivedAt":"2009-01-22T16:57:23Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n> Felipe Contreras writes:\n>\n>> This brings back my previous question: where is the home directory in\n>> a Windows system?\n>\n> It's where %HOMEDRIVE%%HOMEPATH% points to.\n\nI thought it was something like that. Do we want something like that\nin the manual, or should we assume Windows users know that?\n\n-- \nFelipe Contreras\n"},{"id":"101548","messageId":"7v1vuv8dqy.fsf@gitster.siamese.dyndns.org","threadId":"17287","inReplyTo":"94a0d4530901220857q1027c05bs137dcc0244a1cc5a@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-01-22T17:14:13Z","receivedAt":"2009-01-22T17:14:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Felipe Contreras writes:\n\n> On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n>> Felipe Contreras writes:\n>>\n>>> This brings back my previous question: where is the home directory in\n>>> a Windows system?\n>>\n>> It's where %HOMEDRIVE%%HOMEPATH% points to.\n>\n> I thought it was something like that. Do we want something like that\n> in the manual, or should we assume Windows users know that?\n\nFunny; while I was test driving Msysgit (I wrote the report in my blog\npages some time ago), I got curious about this exact issue. I thought the\nchoice of $HOME at that path was quite natural even for me who does not\nusually use Windows.\n"},{"id":"101552","messageId":"alpine.DEB.1.00.0901221827370.3586@pacific.mpi-cbg.de","threadId":"17287","inReplyTo":"7v1vuv8dqy.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-01-22T17:28:12Z","receivedAt":"2009-01-22T17:28:12Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 22 Jan 2009, Junio C Hamano wrote:\n\n> Felipe Contreras writes:\n> \n> > On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n> >> Felipe Contreras writes:\n> >>\n> >>> This brings back my previous question: where is the home directory in\n> >>> a Windows system?\n> >>\n> >> It's where %HOMEDRIVE%%HOMEPATH% points to.\n> >\n> > I thought it was something like that. Do we want something like that\n> > in the manual, or should we assume Windows users know that?\n> \n> Funny; while I was test driving Msysgit (I wrote the report in my blog\n> pages some time ago), I got curious about this exact issue. I thought the\n> choice of $HOME at that path was quite natural even for me who does not\n> usually use Windows.\n\nThat's what they said when they convinced me that /home// was not a \nnatural place on Windows.\n\nCiao,\nDscho\n"},{"id":"101556","messageId":"83wscndv57.fsf@kalahari.s2.org","threadId":"17287","inReplyTo":"94a0d4530901220857q1027c05bs137dcc0244a1cc5a@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Hannu Koivisto","fromEmail":"azure@iki.fi","sentAt":"2009-01-22T18:59:32Z","receivedAt":"2009-01-22T18:59:32Z","isPatch":true,"sender":{"key":"azure@iki.fi","avatar":null},"body":"Felipe Contreras writes:\n\n> On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n>> Felipe Contreras writes:\n>>\n>>> This brings back my previous question: where is the home directory in\n>>> a Windows system?\n>>\n>> It's where %HOMEDRIVE%%HOMEPATH% points to.\n>\n> I thought it was something like that. Do we want something like that\n> in the manual, or should we assume Windows users know that?\n\nI should have added that Unix programs (i.e. Cygwin programs and\neven some native ports) probably use %HOME% which may be different\nfrom %HOMEDRIVE%%HOMEPATH%. I recall that if you haven't\nexplicitly set up HOME in Windows environment, Cygwin sets it up\nmagically from passwd or falls back to %HOMEDRIVE%%HOMEPATH%. I\nhave no idea if msysgit respects %HOME% if it is set or always uses\n%HOMEDRIVE%%HOMEPATH% or something completely different (user\nprofile, most likely).\n\nIt certainly may be that \"home directory\" is a foreign concept to\nsome Windows users. Some might know it as a user profile or a\npersonal folder (just guessing, I'm pretty isolated from less\nexperienced Windows users), even though user profile is a separate\nconcept from \"home directory\" (note that there is %USERPROFILE%\nwhich by default is the same as %HOMEDRIVE%%HOMEPATH% at least in\nXP).\n\nIn any case, what Cygwin git does should be expected by Cygwin\nusers. If msysgit wanted to be a really native Windows application\nand store the configuration where Microsoft thinks it should be\nstored, it probably shouldn't store the config under \"home\ndirectory\" to begin with (I'm guessing that's what it does) but\nunder %USERPROFILE\\Application Data\\Git (...FILE\\Local\nSettings\\... in case non-roaming storage is wanted). And in that\ncase the manual might be misleading for msysgit users. See\ne.g. .\n\n-- \nHannu\n"},{"id":"101733","messageId":"94a0d4530901240021u65adeff8pb6995ef707bc1f68@mail.gmail.com","threadId":"17287","inReplyTo":"83wscndv57.fsf@kalahari.s2.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-24T08:21:14Z","receivedAt":"2009-01-24T08:21:14Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Thu, Jan 22, 2009 at 8:59 PM, Hannu Koivisto wrote:\n> Felipe Contreras writes:\n>\n>> On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n>>> Felipe Contreras writes:\n>>>\n>>>> This brings back my previous question: where is the home directory in\n>>>> a Windows system?\n>>>\n>>> It's where %HOMEDRIVE%%HOMEPATH% points to.\n>>\n>> I thought it was something like that. Do we want something like that\n>> in the manual, or should we assume Windows users know that?\n>\n> I should have added that Unix programs (i.e. Cygwin programs and\n> even some native ports) probably use %HOME% which may be different\n> from %HOMEDRIVE%%HOMEPATH%. I recall that if you haven't\n> explicitly set up HOME in Windows environment, Cygwin sets it up\n> magically from passwd or falls back to %HOMEDRIVE%%HOMEPATH%. I\n> have no idea if msysgit respects %HOME% if it is set or always uses\n> %HOMEDRIVE%%HOMEPATH% or something completely different (user\n> profile, most likely).\n>\n> It certainly may be that \"home directory\" is a foreign concept to\n> some Windows users. Some might know it as a user profile or a\n> personal folder (just guessing, I'm pretty isolated from less\n> experienced Windows users), even though user profile is a separate\n> concept from \"home directory\" (note that there is %USERPROFILE%\n> which by default is the same as %HOMEDRIVE%%HOMEPATH% at least in\n> XP).\n>\n> In any case, what Cygwin git does should be expected by Cygwin\n> users. If msysgit wanted to be a really native Windows application\n> and store the configuration where Microsoft thinks it should be\n> stored, it probably shouldn't store the config under \"home\n> directory\" to begin with (I'm guessing that's what it does) but\n> under %USERPROFILE\\Application Data\\Git (...FILE\\Local\n> Settings\\... in case non-roaming storage is wanted). And in that\n> case the manual might be misleading for msysgit users. See\n> e.g. .\n\nIsn't that enough argument to stop assuming the user knows where is\nthe \"home directory\"?\n\n-- \nFelipe Contreras\n"},{"id":"101739","messageId":"alpine.DEB.1.00.0901241438370.13232@racer","threadId":"17287","inReplyTo":"94a0d4530901240021u65adeff8pb6995ef707bc1f68@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-01-24T13:42:20Z","receivedAt":"2009-01-24T13:42:20Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 24 Jan 2009, Felipe Contreras wrote:\n\n> On Thu, Jan 22, 2009 at 8:59 PM, Hannu Koivisto wrote:\n> > Felipe Contreras writes:\n> >\n> >> On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n> >>> Felipe Contreras writes:\n> >>>\n> >>>> This brings back my previous question: where is the home directory in\n> >>>> a Windows system?\n> >>>\n> >>> It's where %HOMEDRIVE%%HOMEPATH% points to.\n> >>\n> >> I thought it was something like that. Do we want something like that\n> >> in the manual, or should we assume Windows users know that?\n> >\n> > I should have added that Unix programs (i.e. Cygwin programs and\n> > even some native ports) probably use %HOME% which may be different\n> > from %HOMEDRIVE%%HOMEPATH%. I recall that if you haven't\n> > explicitly set up HOME in Windows environment, Cygwin sets it up\n> > magically from passwd or falls back to %HOMEDRIVE%%HOMEPATH%. I\n> > have no idea if msysgit respects %HOME% if it is set or always uses\n> > %HOMEDRIVE%%HOMEPATH% or something completely different (user\n> > profile, most likely).\n> >\n> > It certainly may be that \"home directory\" is a foreign concept to\n> > some Windows users. Some might know it as a user profile or a\n> > personal folder (just guessing, I'm pretty isolated from less\n> > experienced Windows users), even though user profile is a separate\n> > concept from \"home directory\" (note that there is %USERPROFILE%\n> > which by default is the same as %HOMEDRIVE%%HOMEPATH% at least in\n> > XP).\n> >\n> > In any case, what Cygwin git does should be expected by Cygwin\n> > users. If msysgit wanted to be a really native Windows application\n> > and store the configuration where Microsoft thinks it should be\n> > stored, it probably shouldn't store the config under \"home\n> > directory\" to begin with (I'm guessing that's what it does) but\n> > under %USERPROFILE\\Application Data\\Git (...FILE\\Local\n> > Settings\\... in case non-roaming storage is wanted). And in that\n> > case the manual might be misleading for msysgit users. See\n> > e.g. .\n> \n> Isn't that enough argument to stop assuming the user knows where is\n> the \"home directory\"?\n\nWhy does it appear as if we always have to bend over for Windows? That is \nreally frustrating.\n\nIn any case, the only thing the user would need to know the location of \n$HOME for is for .gitconfig. And for Windows users I suggest using the \ndialog in git gui (for the variables that are editable there), which \nshould cover most of what the user needs. For everything else, they \nshould use \"git config\".\n\nBecause if you really start with explaining where the home can be on \nWindows, you would also have to cover why \"%USERPROFILE%\" does not work in \nGit bash. And before you know what is happening, you have a big ass \nWindows chapter in the user manual that revolves around anything except \nGit.\n\nCiao,\nDscho\n"},{"id":"101741","messageId":"94a0d4530901240604o5ae0d321h17dc6aabeefe9d53@mail.gmail.com","threadId":"17287","inReplyTo":"alpine.DEB.1.00.0901241438370.13232@racer","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-24T14:04:11Z","receivedAt":"2009-01-24T14:04:11Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Sat, Jan 24, 2009 at 3:42 PM, Johannes Schindelin\n wrote:\n> Hi,\n>\n> On Sat, 24 Jan 2009, Felipe Contreras wrote:\n>\n>> On Thu, Jan 22, 2009 at 8:59 PM, Hannu Koivisto wrote:\n>> > Felipe Contreras writes:\n>> >\n>> >> On Thu, Jan 22, 2009 at 6:17 PM, Hannu Koivisto wrote:\n>> >>> Felipe Contreras writes:\n>> >>>\n>> >>>> This brings back my previous question: where is the home directory in\n>> >>>> a Windows system?\n>> >>>\n>> >>> It's where %HOMEDRIVE%%HOMEPATH% points to.\n>> >>\n>> >> I thought it was something like that. Do we want something like that\n>> >> in the manual, or should we assume Windows users know that?\n>> >\n>> > I should have added that Unix programs (i.e. Cygwin programs and\n>> > even some native ports) probably use %HOME% which may be different\n>> > from %HOMEDRIVE%%HOMEPATH%. I recall that if you haven't\n>> > explicitly set up HOME in Windows environment, Cygwin sets it up\n>> > magically from passwd or falls back to %HOMEDRIVE%%HOMEPATH%. I\n>> > have no idea if msysgit respects %HOME% if it is set or always uses\n>> > %HOMEDRIVE%%HOMEPATH% or something completely different (user\n>> > profile, most likely).\n>> >\n>> > It certainly may be that \"home directory\" is a foreign concept to\n>> > some Windows users. Some might know it as a user profile or a\n>> > personal folder (just guessing, I'm pretty isolated from less\n>> > experienced Windows users), even though user profile is a separate\n>> > concept from \"home directory\" (note that there is %USERPROFILE%\n>> > which by default is the same as %HOMEDRIVE%%HOMEPATH% at least in\n>> > XP).\n>> >\n>> > In any case, what Cygwin git does should be expected by Cygwin\n>> > users. If msysgit wanted to be a really native Windows application\n>> > and store the configuration where Microsoft thinks it should be\n>> > stored, it probably shouldn't store the config under \"home\n>> > directory\" to begin with (I'm guessing that's what it does) but\n>> > under %USERPROFILE\\Application Data\\Git (...FILE\\Local\n>> > Settings\\... in case non-roaming storage is wanted). And in that\n>> > case the manual might be misleading for msysgit users. See\n>> > e.g. .\n>>\n>> Isn't that enough argument to stop assuming the user knows where is\n>> the \"home directory\"?\n>\n> Why does it appear as if we always have to bend over for Windows? That is\n> really frustrating.\n>\n> In any case, the only thing the user would need to know the location of\n> $HOME for is for .gitconfig. And for Windows users I suggest using the\n> dialog in git gui (for the variables that are editable there), which\n> should cover most of what the user needs. For everything else, they\n> should use \"git config\".\n>\n> Because if you really start with explaining where the home can be on\n> Windows, you would also have to cover why \"%USERPROFILE%\" does not work in\n> Git bash. And before you know what is happening, you have a big ass\n> Windows chapter in the user manual that revolves around anything except\n> Git.\n\nHuh? That was exactly my point.\n\nIt's much easier for everyone to just use git config --global than\nexplain how create and edit the .gitconfig file. If this is explained\nit shouldn't be in the \"Telling git your name\" section.\n\n-- \nFelipe Contreras\n"},{"id":"101820","messageId":"f73f7ab80901242332x7de1f856j51181c3c05cf2b11@mail.gmail.com","threadId":"17287","inReplyTo":"83wscndv57.fsf@kalahari.s2.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Kyle Moffett","fromEmail":"kyle@moffetthome.net","sentAt":"2009-01-25T07:32:38Z","receivedAt":"2009-01-25T07:32:38Z","isPatch":true,"sender":{"key":"kyle@moffetthome.net","avatar":null},"body":"On Thu, Jan 22, 2009 at 1:59 PM, Hannu Koivisto wrote:\n> In any case, what Cygwin git does should be expected by Cygwin\n> users. If msysgit wanted to be a really native Windows application\n> and store the configuration where Microsoft thinks it should be\n> stored, it probably shouldn't store the config under \"home\n> directory\" to begin with (I'm guessing that's what it does) but\n> under %USERPROFILE\\Application Data\\Git (...FILE\\Local\n> Settings\\... in case non-roaming storage is wanted). And in that\n> case the manual might be misleading for msysgit users. See\n> e.g. .\n\nActually, if msysgit really wanted to be a \"native\" windows program,\nit would use the good-old brain-damaged method of storing\neverything-and-the-kitchen-sink in the registry, including the\nlocations and reflogs for every repository you have ever examined.\nAdmittedly the collection of 150+ dotfiles in my Linux homedir looks\nrelatively similar to parts of the windows registry at times...\n\nCheers,\nKyle Moffett\n"},{"id":"101827","messageId":"alpine.DEB.1.00.0901251301000.14855@racer","threadId":"17287","inReplyTo":"f73f7ab80901242332x7de1f856j51181c3c05cf2b11@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-01-25T12:06:01Z","receivedAt":"2009-01-25T12:06:01Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sun, 25 Jan 2009, Kyle Moffett wrote:\n\n> Actually, if msysgit really wanted to be a \"native\" windows program,\n\n... it would\n\n- not use MSys, but MSVC++,\n\n- have a backing by a startup company,\n\n- not use any of Git's source code at all, but reimplement everything in \n closed source,\n\n- come with a shrink wrapped box and a huge manual,\n\n- do a lot of BS advertisement,\n\n- offer overprized courses for management, in fancy locations,\n\n- would cost around 50 dollars for a single license,\n\n- would cost around 1500 dollars for a site-wide license with free \n upgrades for 3 years and 2 free training courses,\n\n- be dog slow, eating resources like mad, and\n\n- crash frequently.\n\nOther questions?\n\nCiao,\nDscho\n"},{"id":"101867","messageId":"7vvds3dszy.fsf@gitster.siamese.dyndns.org","threadId":"17287","inReplyTo":"94a0d4530901240604o5ae0d321h17dc6aabeefe9d53@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-01-25T20:34:57Z","receivedAt":"2009-01-25T20:34:57Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Felipe Contreras writes:\n\n> It's much easier for everyone to just use git config --global than\n> explain how create and edit the .gitconfig file. If this is explained\n> it shouldn't be in the \"Telling git your name\" section.\n\nI think it is Ok to have, and it probably is helpful to have, a document\nthat accompanies the generic manual, \"Platform supplement\", to explain\nthings like \"On this platform, what is referred to as $HOME in the generic\nmanual is implemented as %HOMEDRIVE%%HOMEPATH%\", to cover peculiarities of\neach platform.\n\nBut I think it is going backwards to butcher the description in the main\nmanual in order to make the platform supplement shorter. Even Windows is\nnot a good enough reason to break the logical ordering of how things\nshould be best taught to the readers of the manual, which is not specific\nto a platform.\n"},{"id":"101879","messageId":"94a0d4530901251312q4201d51btd806fe860a12afd6@mail.gmail.com","threadId":"17287","inReplyTo":"7vvds3dszy.fsf@gitster.siamese.dyndns.org","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2009-01-25T21:12:57Z","receivedAt":"2009-01-25T21:12:57Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Sun, Jan 25, 2009 at 10:34 PM, Junio C Hamano wrote:\n> Felipe Contreras writes:\n>\n>> It's much easier for everyone to just use git config --global than\n>> explain how create and edit the .gitconfig file. If this is explained\n>> it shouldn't be in the \"Telling git your name\" section.\n>\n> I think it is Ok to have, and it probably is helpful to have, a document\n> that accompanies the generic manual, \"Platform supplement\", to explain\n> things like \"On this platform, what is referred to as $HOME in the generic\n> manual is implemented as %HOMEDRIVE%%HOMEPATH%\", to cover peculiarities of\n> each platform.\n>\n> But I think it is going backwards to butcher the description in the main\n> manual in order to make the platform supplement shorter. Even Windows is\n> not a good enough reason to break the logical ordering of how things\n> should be best taught to the readers of the manual, which is not specific\n> to a platform.\n\nThat's why I think there should be a whole section regarding git\nconfiguration before \"Telling git your name\".\n\nHowever, my last proposal was to have both the git config --global\n*and* the $HOME/.gitconfig description. Is there any argument against\nthat?\n\n-- \nFelipe Contreras\n"},{"id":"101881","messageId":"20090125214435.GA20173@coredump.intra.peff.net","threadId":"17287","inReplyTo":"94a0d4530901251312q4201d51btd806fe860a12afd6@mail.gmail.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-25T21:44:35Z","receivedAt":"2009-01-25T21:44:35Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Jan 25, 2009 at 11:12:57PM +0200, Felipe Contreras wrote:\n\n> However, my last proposal was to have both the git config --global\n> *and* the $HOME/.gitconfig description. Is there any argument against\n> that?\n\nThis is like the fifth time you have asked, and for some reason, nobody\nseems to have said yes or no. So I will go ahead and say: yes, I think\nthat is a fine idea.\n\nI think there should also be some explanatory text that indicates they\nare totally interchangeable for the rest of the document. Something\nlike: \"When we show configuration in the rest of this document, we will\nuse format X [I think probably \"git config $VAR $VALUE\"]. But you can\nuse whichever method you are most comfortable with.\"\n\n-Peff\n"},{"id":"101892","messageId":"190FD80D-0F10-4C76-9029-1434F362EFDB@wincent.com","threadId":"17287","inReplyTo":"20090125214435.GA20173@coredump.intra.peff.net","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Wincent Colaiuta","fromEmail":"win@wincent.com","sentAt":"2009-01-25T22:55:24Z","receivedAt":"2009-01-25T22:55:24Z","isPatch":true,"sender":{"key":"greg@hurrell.net","avatar":"https://avatars.githubusercontent.com/u/7074?v=4"},"body":"El 25/1/2009, a las 22:44, Jeff King escribió:\n\n> On Sun, Jan 25, 2009 at 11:12:57PM +0200, Felipe Contreras wrote:\n>\n>> However, my last proposal was to have both the git config --global\n>> *and* the $HOME/.gitconfig description. Is there any argument against\n>> that?\n>\n> This is like the fifth time you have asked, and for some reason, \n> nobody\n> seems to have said yes or no. So I will go ahead and say: yes, I think\n> that is a fine idea.\n>\n> I think there should also be some explanatory text that indicates they\n> are totally interchangeable for the rest of the document. Something\n> like: \"When we show configuration in the rest of this document, we \n> will\n> use format X [I think probably \"git config $VAR $VALUE\"]. But you can\n> use whichever method you are most comfortable with.\"\n\nI already suggested something similar about 4 days ago:\n\nhttp://article.gmane.org/gmane.comp.version-control.git/106673/\n\nCheers,\nWincent\n"},{"id":"101899","messageId":"20090125231959.GA19099@coredump.intra.peff.net","threadId":"17287","inReplyTo":"190FD80D-0F10-4C76-9029-1434F362EFDB@wincent.com","subject":"Re: [PATCH 1/2] user-manual: Simplify the user configuration.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-01-25T23:20:00Z","receivedAt":"2009-01-25T23:20:00Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Jan 25, 2009 at 11:55:24PM +0100, Wincent Colaiuta wrote:\n\n>> I think there should also be some explanatory text that indicates they\n>> are totally interchangeable for the rest of the document. Something\n>> like: \"When we show configuration in the rest of this document, we will\n>> use format X [I think probably \"git config $VAR $VALUE\"]. But you can\n>> use whichever method you are most comfortable with.\"\n>\n> I already suggested something similar about 4 days ago:\n>\n> http://article.gmane.org/gmane.comp.version-control.git/106673/\n\nOh, I think I must have mixed up reading your post and thinking it was\nfrom Felipe. Sorry.\n\nAt any rate, I think what you wrote there is sensible.\n\n-Peff\n"}]}