{"thread":{"id":"16996","subject":"[PATCH 2/2] Be consistent in switch usage for tar","startedAt":"2009-01-05T15:25:35Z","lastAt":"2009-01-06T08:18:45Z","messageCount":5,"participants":["henrik@austad.us","Alexander Potashev","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"99371","messageId":"1231169137-32653-1-git-send-email-henrik@austad.us","threadId":"16996","inReplyTo":null,"subject":"Consistency patches for Documentation/","fromName":"","fromEmail":"henrik@austad.us","sentAt":"2009-01-05T15:25:35Z","receivedAt":"2009-01-05T15:25:35Z","isPatch":false,"sender":{"key":"henrik@austad.us","avatar":"https://gravatar.com/avatar/c3f6bb245c70f4ee4c8af7c4b067694462f1a35c006daa806d4dd09f914eeed6?d=mp&s=160"},"body":"\nThe following 2 patches are rather pedantic, but should be corrected. \nSorry if the way I've sent these are wrong :)\n"},{"id":"99369","messageId":"1231169137-32653-2-git-send-email-henrik@austad.us","threadId":"16996","inReplyTo":"1231169137-32653-1-git-send-email-henrik@austad.us","subject":"[PATCH 1/2] Use capitalized names where appropriate","fromName":"","fromEmail":"henrik@austad.us","sentAt":"2009-01-05T15:25:36Z","receivedAt":"2009-01-05T15:25:36Z","isPatch":true,"sender":{"key":"henrik@austad.us","avatar":"https://gravatar.com/avatar/c3f6bb245c70f4ee4c8af7c4b067694462f1a35c006daa806d4dd09f914eeed6?d=mp&s=160"},"body":"From: Henrik Austad <henrik@austad.us>\n\nThe Linux kernel and Emacs are both spelled capitalized\n\nSigned-off-by: Henrik Austad <henrik@austad.us>\n---\n Documentation/gittutorial.txt |    4 ++--\n Documentation/user-manual.txt |    4 ++--\n 2 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt\nindex 7892244..458fafd 100644\n--- a/Documentation/gittutorial.txt\n+++ b/Documentation/gittutorial.txt\n@@ -590,7 +590,7 @@ list.  When the history has lines of development that diverged and\n then merged back together, the order in which 'git-log' presents\n those commits is meaningless.\n \n-Most projects with multiple contributors (such as the linux kernel,\n+Most projects with multiple contributors (such as the Linux kernel,\n or git itself) have frequent merges, and 'gitk' does a better job of\n visualizing their history.  For example,\n \n@@ -642,7 +642,7 @@ digressions that may be interesting at this point are:\n \n   * linkgit:git-format-patch[1], linkgit:git-am[1]: These convert\n     series of git commits into emailed patches, and vice versa,\n-    useful for projects such as the linux kernel which rely heavily\n+    useful for projects such as the Linux kernel which rely heavily\n     on emailed patches.\n \n   * linkgit:git-bisect[1]: When there is a regression in your\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex d4b1e90..5242a7e 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -59,7 +59,7 @@ project in mind, here are some interesting examples:\n ------------------------------------------------\n \t# git itself (approx. 10MB download):\n $ git clone git://git.kernel.org/pub/scm/git/git.git\n-\t# the linux kernel (approx. 150MB download):\n+\t# the Linux kernel (approx. 150MB download):\n $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git\n ------------------------------------------------\n \n@@ -1340,7 +1340,7 @@ These will display all commits which exist only on HEAD or on\n MERGE_HEAD, and which touch an unmerged file.\n \n You may also use linkgit:git-mergetool[1], which lets you merge the\n-unmerged files using external tools such as emacs or kdiff3.\n+unmerged files using external tools such as Emacs or kdiff3.\n \n Each time you resolve the conflicts in a file and update the index:\n \n-- \n1.6.1.36.g8430e\n"},{"id":"99368","messageId":"1231169137-32653-3-git-send-email-henrik@austad.us","threadId":"16996","inReplyTo":"1231169137-32653-2-git-send-email-henrik@austad.us","subject":"[PATCH 2/2] Be consistent in switch usage for tar","fromName":"","fromEmail":"henrik@austad.us","sentAt":"2009-01-05T15:25:37Z","receivedAt":"2009-01-05T15:25:37Z","isPatch":true,"sender":{"key":"henrik@austad.us","avatar":"https://gravatar.com/avatar/c3f6bb245c70f4ee4c8af7c4b067694462f1a35c006daa806d4dd09f914eeed6?d=mp&s=160"},"body":"From: Henrik Austad <henrik@austad.us>\n\ntar handles switches with and witouth preceding '-', but the documentation should be\nconsistent nonetheless.\n\nSigned-off-by: Henrik Austad <henrik@austad.us>\n---\n Documentation/user-manual.txt |    2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex 5242a7e..19f571a 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -1009,7 +1009,7 @@ $ git init\n If you have some initial content (say, a tarball):\n \n -------------------------------------------------\n-$ tar -xzvf project.tar.gz\n+$ tar xzvf project.tar.gz\n $ cd project\n $ git init\n $ git add . # include everything below ./ in the first commit:\n-- \n1.6.1.36.g8430e\n"},{"id":"99374","messageId":"20090105181950.GA5403@myhost","threadId":"16996","inReplyTo":"1231169137-32653-3-git-send-email-henrik@austad.us","subject":"Re: [PATCH 2/2] Be consistent in switch usage for tar","fromName":"Alexander Potashev","fromEmail":"aspotashev@gmail.com","sentAt":"2009-01-05T18:19:50Z","receivedAt":"2009-01-05T18:19:50Z","isPatch":true,"sender":{"key":"aspotashev@gmail.com","avatar":null},"body":"On 16:25 Mon 05 Jan     , henrik@austad.us wrote:\n> From: Henrik Austad <henrik@austad.us>\n> \n> tar handles switches with and witouth preceding '-', but the documentation should be\n\ns/witouth/without\n\n> consistent nonetheless.\n> \n> Signed-off-by: Henrik Austad <henrik@austad.us>\n> ---\n>  Documentation/user-manual.txt |    2 +-\n>  1 files changed, 1 insertions(+), 1 deletions(-)\n> \n> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> index 5242a7e..19f571a 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n> @@ -1009,7 +1009,7 @@ $ git init\n>  If you have some initial content (say, a tarball):\n>  \n>  -------------------------------------------------\n> -$ tar -xzvf project.tar.gz\n> +$ tar xzvf project.tar.gz\n\nBtw, tar manpage uses dashed options in usage examples:\n\n\ttar -xvf foo.tar\n\t\tverbosely extract foo.tar\n\t...\n\n\n>  $ cd project\n>  $ git init\n>  $ git add . # include everything below ./ in the first commit:\n> -- \n> 1.6.1.36.g8430e\n"},{"id":"99438","messageId":"7vtz8ckftm.fsf@gitster.siamese.dyndns.org","threadId":"16996","inReplyTo":"1231169137-32653-3-git-send-email-henrik@austad.us","subject":"Re: [PATCH 2/2] Be consistent in switch usage for tar","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-01-06T08:18:45Z","receivedAt":"2009-01-06T08:18:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks; both patches applied.\n"}]}