{"thread":{"id":"8014","subject":"Re: [PATCH 5/6] user-manual: miscellaneous editing","startedAt":"2007-05-07T07:27:40Z","lastAt":"2007-05-08T10:12:37Z","messageCount":5,"participants":["Santi Béjar","J. Bruce Fields","Karl Hasselström"],"isPatch":true,"patchVersion":1,"patchTotal":6},"messages":[{"id":"41296","messageId":"8aa486160705070027g2cb6797fy5acbe338e30429ff@mail.gmail.com","threadId":"8014","inReplyTo":"-1060540797535999820@unknownmsgid","subject":"Re: [PATCH 5/6] user-manual: miscellaneous editing","fromName":"Santi Béjar","fromEmail":"sbejar@gmail.com","sentAt":"2007-05-07T07:27:40Z","receivedAt":"2007-05-07T07:27:40Z","isPatch":true,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On 5/7/07, J. Bruce Fields <bfields@citi.umich.edu> wrote:\n> From: J. Bruce Fields <bfields@citi.umich.edu>\n>\n> I cherry-picked some additional miscellaneous fixes from those suggested\n> by Santi Béjar, including fixes to:\n>\n>         - correct discussion of repository/HEAD->repository shortcut\n>         - add mention of git-mergetool\n>         - add mention of --track\n>         - mention \"-f\" as well as \"+\" for fetch\n>\n\n> Cc: Santi Béjar <sbejar@gmail.com>\n\nYou forgot to CC: the e-mail to me :-)\n\n> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> index c292b4d..67f5b9b 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n\n[...]\n\n> @@ -1830,14 +1836,14 @@ Now, assume your personal repository is in the directory ~/proj.  We\n>  first create a new clone of the repository:\n>\n>  -------------------------------------------------\n> -$ git clone --bare proj-clone.git\n> +$ git clone --bare proj.git\n>  -------------------------------------------------\n\nYou missed the ~/proj as in:\n\n$ git clone --bare ~/proj proj.git\n\nWhat do you think about the rest of my changes, in particular:\n\n@@ -2374,7 +2388,6 @@ then the following commands will all do the same thing:\n -------------------------------------------------\n $ git fetch git://example.com/proj.git master:ref/remotes/example/master\n $ git fetch example master:ref/remotes/example/master\n-$ git fetch example example/master\n $ git fetch example\n -------------------------------------------------\n\nSanti\n"},{"id":"41395","messageId":"20070508030732.GB9471@fieldses.org","threadId":"8014","inReplyTo":"8aa486160705070027g2cb6797fy5acbe338e30429ff@mail.gmail.com","subject":"Re: [PATCH 5/6] user-manual: miscellaneous editing","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-05-08T03:07:32Z","receivedAt":"2007-05-08T03:07:32Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Mon, May 07, 2007 at 09:27:40AM +0200, Santi Béjar wrote:\n> On 5/7/07, J. Bruce Fields <bfields@citi.umich.edu> wrote:\n> >Cc: Santi Béjar <sbejar@gmail.com>\n>\n> You forgot to CC: the e-mail to me :-)\n\nThe version of git-send-email I was using is supposed to do that\nautomatically based on the inlined Cc: line.  Did it not do that?\n\n> >@@ -1830,14 +1836,14 @@ Now, assume your personal repository is in the \n> >directory ~/proj.  We\n> > first create a new clone of the repository:\n> >\n> > -------------------------------------------------\n> >-$ git clone --bare proj-clone.git\n> >+$ git clone --bare proj.git\n> > -------------------------------------------------\n> \n> You missed the ~/proj as in:\n> \n> $ git clone --bare ~/proj proj.git\n\nWhoops, thanks.\n\n> What do you think about the rest of my changes, in particular:\n> \n> @@ -2374,7 +2388,6 @@ then the following commands will all do the same \n> thing:\n> -------------------------------------------------\n> $ git fetch git://example.com/proj.git master:ref/remotes/example/master\n> $ git fetch example master:ref/remotes/example/master\n> -$ git fetch example example/master\n> $ git fetch example\n> -------------------------------------------------\n\nYes, you're correct, thanks for your persistence.\n\nThe others--I don't remember.  I'll take a quick look.  If you want to\nbe sure they'll all be considered, you could update the patch and\nresend.\n\n--b.\n"},{"id":"41402","messageId":"20070508033426.GD9471@fieldses.org","threadId":"8014","inReplyTo":"20070508030732.GB9471@fieldses.org","subject":"[PATCH] user-manual: fix clone and fetch typos","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-05-08T03:34:26Z","receivedAt":"2007-05-08T03:34:26Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"More typo fixes from Santi Béjar, plus a couple other mistakes I noticed\nalong the way.\n\nCc: Santi Béjar <sbejar@gmail.com>\nSigned-off-by: \"J. Bruce Fields\" <bfields@citi.umich.edu>\n---\n Documentation/user-manual.txt |   13 ++++++-------\n 1 files changed, 6 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex 67f5b9b..13db969 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -1836,12 +1836,12 @@ Now, assume your personal repository is in the directory ~/proj.  We\n first create a new clone of the repository:\n \n -------------------------------------------------\n-$ git clone --bare proj.git\n+$ git clone --bare ~/proj proj.git\n -------------------------------------------------\n \n-The resulting directory proj.git will contains a \"bare\" git\n-repository--it is just the contents of the \".git\" directory, without\n-a checked-out copy of a working directory.\n+The resulting directory proj.git contains a \"bare\" git repository--it is\n+just the contents of the \".git\" directory, without a checked-out copy of\n+a working directory.\n \n Next, copy proj.git to the server where you plan to host the\n public repository.  You can use scp, rsync, or whatever is most\n@@ -2372,9 +2372,8 @@ $ git config remote.example.fetch master:refs/remotes/example/master\n then the following commands will all do the same thing:\n \n -------------------------------------------------\n-$ git fetch git://example.com/proj.git master:ref/remotes/example/master\n-$ git fetch example master:ref/remotes/example/master\n-$ git fetch example example/master\n+$ git fetch git://example.com/proj.git master:refs/remotes/example/master\n+$ git fetch example master:refs/remotes/example/master\n $ git fetch example\n -------------------------------------------------\n \n-- \n1.5.1.1.98.gedb4f\n"},{"id":"41405","messageId":"20070508034129.GE9471@fieldses.org","threadId":"8014","inReplyTo":"20070508033426.GD9471@fieldses.org","subject":"Re: [PATCH] user-manual: fix clone and fetch typos","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-05-08T03:41:29Z","receivedAt":"2007-05-08T03:41:29Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Mon, May 07, 2007 at 11:34:26PM -0400, J. Bruce Fields wrote:\n> More typo fixes from Santi Béjar, plus a couple other mistakes I noticed\n> along the way.\n> \n> Cc: Santi Béjar <sbejar@gmail.com>\n> Signed-off-by: \"J. Bruce Fields\" <bfields@citi.umich.edu>\n\nHm.  I still see\n\n\tContent-Type:   text/plain; charset=iso-8859-1\n\nin the headers, even in the copy saved in my sent-mail folder.  My\nlocale seems to be set to something utf-8-ish everywhere, though.  Is\nthere some odd mutt configuration setting I'm missing someplace?\nCharacter sets mystify me....\n\n--b.\n"},{"id":"41435","messageId":"20070508101237.GA27119@diana.vm.bytemark.co.uk","threadId":"8014","inReplyTo":"20070508034129.GE9471@fieldses.org","subject":"Re: [PATCH] user-manual: fix clone and fetch typos","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2007-05-08T10:12:37Z","receivedAt":"2007-05-08T10:12:37Z","isPatch":true,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2007-05-07 23:41:29 -0400, J. Bruce Fields wrote:\n\n> Hm.  I still see\n>\n>       Content-Type:   text/plain; charset=iso-8859-1\n>\n> in the headers\n\nBut this time, it looks good to me. This is probably because the\nheaders say the body is QP-encoded latin1:\n\n  Content-Type:   text/plain; charset=iso-8859-1\n  Content-Transfer-Encoding: QUOTED-PRINTABLE\n\nand the body actually _is_ QP-encoded latin1:\n\n  More typo fixes from Santi B=E9jar\n\nNote how the \"é\" is encoded with only one byte this time, like it's\nsupposed to in latin1.\n\n-- \nKarl Hasselström, kha@treskal.com\n      www.treskal.com/kalle\n"}]}