{"thread":{"id":"2064","subject":"[PATCH] Convert usage of GIT and Git into git","startedAt":"2005-10-10T21:26:31Z","lastAt":"2005-10-11T06:27:40Z","messageCount":4,"participants":["Christian Meder","James Cloos","Adrien Beau"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"9933","messageId":"1128979592.7097.38.camel@localhost","threadId":"2064","inReplyTo":null,"subject":"[PATCH] Convert usage of GIT and Git into git","fromName":"Christian Meder","fromEmail":"chris@absolutegiganten.org","sentAt":"2005-10-10T21:26:31Z","receivedAt":"2005-10-10T21:26:31Z","isPatch":true,"sender":{"key":"chris@absolutegiganten.org","avatar":null},"body":"Convert usage of GIT and Git into git.\n\nSigned-off-by: Christian Meder <chris@absolutegiganten.org>\n\n---\n\n Documentation/cvs-migration.txt       |   14 +++++++-------\n Documentation/diff-format.txt         |    2 +-\n Documentation/diffcore.txt            |    2 +-\n Documentation/git-apply.txt           |    2 +-\n Documentation/git-archimport.txt      |    8 ++++----\n Documentation/git-clone-pack.txt      |    2 +-\n Documentation/git-convert-objects.txt |    4 ++--\n Documentation/git-cvsimport.txt       |    4 ++--\n Documentation/git-daemon.txt          |    2 +-\n Documentation/git-fetch-pack.txt      |    2 +-\n Documentation/git-fsck-objects.txt    |   10 +++++-----\n Documentation/git-http-fetch.txt      |    4 ++--\n Documentation/git-local-fetch.txt     |    4 ++--\n Documentation/git-pack-objects.txt    |    2 +-\n Documentation/git-peek-remote.txt     |    2 +-\n Documentation/git-rev-parse.txt       |    2 +-\n Documentation/git-show-index.txt      |    2 +-\n Documentation/git-verify-pack.txt     |    4 ++--\n Documentation/git.txt                 |   10 +++++-----\n Documentation/glossary.txt            |    2 +-\n Documentation/hooks.txt               |    2 +-\n Documentation/pull-fetch-param.txt    |    2 +-\n Documentation/repository-layout.txt   |    4 ++--\n Documentation/tutorial.txt            |   18 +++++++++---------\n 24 files changed, 55 insertions(+), 55 deletions(-)\n\n2cfc19a4c9c2d66b642b0968df917938d182fd20\ndiff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt\n--- a/Documentation/cvs-migration.txt\n+++ b/Documentation/cvs-migration.txt\n@@ -1,4 +1,4 @@\n-Git for CVS users\n+git for CVS users\n =================\n \n Ok, so you're a CVS user. That's ok, it's a treatable condition, and the\n@@ -7,7 +7,7 @@ you are reading this file means that you\n already.\n \n The thing about CVS is that it absolutely sucks as a source control\n-manager, and you'll thus be happy with almost anything else. Git,\n+manager, and you'll thus be happy with almost anything else. git,\n however, may be a bit 'too' different (read: \"good\") for your taste, and\n does a lot of things differently. \n \n@@ -15,7 +15,7 @@ One particular suckage of CVS is very ha\n basically a tool for tracking 'file' history, while git is a tool for\n tracking 'project' history.  This sometimes causes problems if you are\n used to doing very strange things in CVS, in particular if you're doing\n-things like making branches of just a subset of the project.  Git can't\n+things like making branches of just a subset of the project.  git can't\n track that, since git never tracks things on the level of an individual\n file, only on the whole project level. \n \n@@ -32,7 +32,7 @@ and notes on converting from CVS to git.\n \n Second: CVS has the notion of a \"repository\" as opposed to the thing\n that you're actually working in (your working directory, or your\n-\"checked out tree\").  Git does not have that notion at all, and all git\n+\"checked out tree\").  git does not have that notion at all, and all git\n working directories 'are' the repositories.  However, you can easily\n emulate the CVS model by having one special \"global repository\", which\n people can synchronize with.  See details later, but in the meantime\n@@ -49,7 +49,7 @@ gone through the git tutorial, and gener\n how to commit stuff etc in git) is to create a git'ified version of your\n CVS archive.\n \n-Happily, that's very easy indeed. Git will do it for you, although git\n+Happily, that's very easy indeed. git will do it for you, although git\n will need the help of a program called \"cvsps\":\n \n \thttp://www.cobite.com/cvsps/\n@@ -135,7 +135,7 @@ technically possible, and there are at l\n there that can be used to get equivalent information (see the git\n mailing list archives for details). \n \n-Git has a couple of alternatives, though, that you may find sufficient\n+git has a couple of alternatives, though, that you may find sufficient\n or even superior depending on your use.  One is called \"git-whatchanged\"\n (for obvious reasons) and the other one is called \"pickaxe\" (\"a tool for\n the software archeologist\"). \n@@ -208,7 +208,7 @@ show anything for commits that do not to\n Also, in the original context, the same statement might have\n appeared at first in a different file and later the file was\n renamed to \"a-file.c\".  CVS annotate would not help you to go\n-back across such a rename, but GIT would still help you in such\n+back across such a rename, but git would still help you in such\n a situation.  For that, you can give the -C flag to\n git-diff-tree, like this:\n \ndiff --git a/Documentation/diff-format.txt b/Documentation/diff-format.txt\n--- a/Documentation/diff-format.txt\n+++ b/Documentation/diff-format.txt\n@@ -106,7 +106,7 @@ For a path that is unmerged, 'GIT_EXTERN\n parameter, <path>.\n \n \n-Git specific extension to diff format\n+git specific extension to diff format\n -------------------------------------\n \n What -p option produces is slightly different from the\ndiff --git a/Documentation/diffcore.txt b/Documentation/diffcore.txt\n--- a/Documentation/diffcore.txt\n+++ b/Documentation/diffcore.txt\n@@ -250,7 +250,7 @@ pattern.  Filepairs that match a glob pa\n in the file are output before ones that match a later line, and\n filepairs that do not match any glob pattern are output last.\n \n-As an example, typical orderfile for the core GIT probably\n+As an example, typical orderfile for the core git probably\n would look like this:\n \n ------------------------------------------------\ndiff --git a/Documentation/git-apply.txt b/Documentation/git-apply.txt\n--- a/Documentation/git-apply.txt\n+++ b/Documentation/git-apply.txt\n@@ -3,7 +3,7 @@ git-apply(1)\n \n NAME\n ----\n-git-apply - Apply patch on a GIT index file and a work tree\n+git-apply - Apply patch on a git index file and a work tree\n \n \n SYNOPSIS\ndiff --git a/Documentation/git-archimport.txt b/Documentation/git-archimport.txt\n--- a/Documentation/git-archimport.txt\n+++ b/Documentation/git-archimport.txt\n@@ -3,7 +3,7 @@ git-archimport(1)\n \n NAME\n ----\n-git-archimport - Import an Arch repository into GIT\n+git-archimport - Import an Arch repository into git \n \n \n SYNOPSIS\n@@ -40,14 +40,14 @@ incremental imports.\n \n MERGES\n ------\n-Patch merge data from Arch is used to mark merges in GIT as well. GIT \n+Patch merge data from Arch is used to mark merges in git as well. git \n does not care much about tracking patches, and only considers a merge when a\n branch incorporates all the commits since the point they forked. The end result\n-is that GIT will have a good idea of how far branches have diverged. So the \n+is that git will have a good idea of how far branches have diverged. So the \n import process does lose some patch-trading metadata.\n \n Fortunately, when you try and merge branches imported from Arch, \n-GIT will find a good merge base, and it has a good chance of identifying \n+git will find a good merge base, and it has a good chance of identifying \n patches that have been traded out-of-sequence between the branches. \n \n OPTIONS\ndiff --git a/Documentation/git-clone-pack.txt b/Documentation/git-clone-pack.txt\n--- a/Documentation/git-clone-pack.txt\n+++ b/Documentation/git-clone-pack.txt\n@@ -28,7 +28,7 @@ OPTIONS\n \tremote side, if it is not found on your $PATH.\n \tInstallations of sshd ignore the user's environment\n \tsetup scripts for login shells (e.g. .bash_profile) and\n-\tyour privately installed GIT may not be found on the system\n+\tyour privately installed git may not be found on the system\n \tdefault $PATH.  Another workaround suggested is to set\n \tup your $PATH in \".bashrc\", but this flag is for people\n \twho do not want to pay the overhead for non-interactive\ndiff --git a/Documentation/git-convert-objects.txt b/Documentation/git-convert-objects.txt\n--- a/Documentation/git-convert-objects.txt\n+++ b/Documentation/git-convert-objects.txt\n@@ -3,7 +3,7 @@ git-convert-objects(1)\n \n NAME\n ----\n-git-convert-objects - Converts old-style GIT repository\n+git-convert-objects - Converts old-style git repository\n \n \n SYNOPSIS\n@@ -12,7 +12,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Converts old-style GIT repository to the latest format\n+Converts old-style git repository to the latest format\n \n \n Author\ndiff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt\n--- a/Documentation/git-cvsimport.txt\n+++ b/Documentation/git-cvsimport.txt\n@@ -10,7 +10,7 @@ SYNOPSIS\n --------\n 'git-cvsimport' [ -o <branch-for-HEAD> ] [ -h ] [ -v ]\n \t\t\t[ -d <CVSROOT> ] [ -p <options-for-cvsps> ]\n-\t\t\t[ -C <GIT_repository> ] [ -i ] [ -k ]\n+\t\t\t[ -C <git_repository> ] [ -i ] [ -k ]\n \t\t\t[ -s <subst> ] [ -m ] [ -M regex ] [ <CVS_module> ]\n \n \n@@ -30,7 +30,7 @@ OPTIONS\n \tare supported.\n \n -C <target-dir>::\n-        The GIT repository to import to.  If the directory doesn't\n+        The git repository to import to.  If the directory doesn't\n         exist, it will be created.  Default is the current directory.\n \n -i::\ndiff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt\n--- a/Documentation/git-daemon.txt\n+++ b/Documentation/git-daemon.txt\n@@ -3,7 +3,7 @@ git-daemon(1)\n \n NAME\n ----\n-git-daemon - A really simple server for GIT repositories.\n+git-daemon - A really simple server for git repositories.\n \n SYNOPSIS\n --------\ndiff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt\n--- a/Documentation/git-fetch-pack.txt\n+++ b/Documentation/git-fetch-pack.txt\n@@ -34,7 +34,7 @@ OPTIONS\n \tremote side, if is not found on your $PATH.\n \tInstallations of sshd ignores the user's environment\n \tsetup scripts for login shells (e.g. .bash_profile) and\n-\tyour privately installed GIT may not be found on the system\n+\tyour privately installed git may not be found on the system\n \tdefault $PATH.  Another workaround suggested is to set\n \tup your $PATH in \".bashrc\", but this flag is for people\n \twho do not want to pay the overhead for non-interactive\ndiff --git a/Documentation/git-fsck-objects.txt b/Documentation/git-fsck-objects.txt\n--- a/Documentation/git-fsck-objects.txt\n+++ b/Documentation/git-fsck-objects.txt\n@@ -41,22 +41,22 @@ index file and all SHA1 references in .g\n \t($GIT_DIR/objects), making sure that it is consistent and\n \tcomplete without referring to objects found in alternate\n \tobject pools listed in GIT_ALTERNATE_OBJECT_DIRECTORIES,\n-\tnor packed GIT archives found in $GIT_DIR/objects/pack;\n+\tnor packed git archives found in $GIT_DIR/objects/pack;\n \tcannot be used with --full.\n \n --full::\n \tCheck not just objects in GIT_OBJECT_DIRECTORY\n \t($GIT_DIR/objects), but also the ones found in alternate\n \tobject pools listed in GIT_ALTERNATE_OBJECT_DIRECTORIES,\n-\tand in packed GIT archives found in $GIT_DIR/objects/pack\n+\tand in packed git archives found in $GIT_DIR/objects/pack\n \tand corresponding pack subdirectories in alternate\n \tobject pools; cannot be used with --standalone.\n \n --strict::\n \tEnable more strict checking, namely to catch a file mode\n \trecorded with g+w bit set, which was created by older\n-\tversions of GIT.  Existing repositories, including the\n-\tLinux kernel, GIT itself, and sparse repository have old\n+\tversions of git.  Existing repositories, including the\n+\tLinux kernel, git itself, and sparse repository have old\n \tobjects that triggers this check, but it is recommended\n \tto check new projects with this flag.\n \n@@ -80,7 +80,7 @@ Any corrupt objects you will have to fin\n the hopes that somebody else has the object you have corrupted).\n \n Of course, \"valid tree\" doesn't mean that it wasn't generated by some\n-evil person, and the end result might be crap. Git is a revision\n+evil person, and the end result might be crap. git is a revision\n tracking system, not a quality assurance system ;)\n \n Extracted Diagnostics\ndiff --git a/Documentation/git-http-fetch.txt b/Documentation/git-http-fetch.txt\n--- a/Documentation/git-http-fetch.txt\n+++ b/Documentation/git-http-fetch.txt\n@@ -3,7 +3,7 @@ git-http-fetch(1)\n \n NAME\n ----\n-git-http-fetch - Downloads a remote GIT repository via HTTP\n+git-http-fetch - Downloads a remote git repository via HTTP\n \n \n SYNOPSIS\n@@ -12,7 +12,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Downloads a remote GIT repository via HTTP.\n+Downloads a remote git repository via HTTP.\n \n -c::\n \tGet the commit objects.\ndiff --git a/Documentation/git-local-fetch.txt b/Documentation/git-local-fetch.txt\n--- a/Documentation/git-local-fetch.txt\n+++ b/Documentation/git-local-fetch.txt\n@@ -3,7 +3,7 @@ git-local-fetch(1)\n \n NAME\n ----\n-git-local-fetch - Duplicates another GIT repository on a local system\n+git-local-fetch - Duplicates another git repository on a local system\n \n \n SYNOPSIS\n@@ -12,7 +12,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Duplicates another GIT repository on a local system.\n+Duplicates another git repository on a local system.\n \n OPTIONS\n -------\ndiff --git a/Documentation/git-pack-objects.txt b/Documentation/git-pack-objects.txt\n--- a/Documentation/git-pack-objects.txt\n+++ b/Documentation/git-pack-objects.txt\n@@ -30,7 +30,7 @@ transport by their peers.\n \n Placing both in the pack/ subdirectory of $GIT_OBJECT_DIRECTORY (or\n any of the directories on $GIT_ALTERNATE_OBJECT_DIRECTORIES)\n-enables GIT to read from such an archive.\n+enables git to read from such an archive.\n \n \n OPTIONS\ndiff --git a/Documentation/git-peek-remote.txt b/Documentation/git-peek-remote.txt\n--- a/Documentation/git-peek-remote.txt\n+++ b/Documentation/git-peek-remote.txt\n@@ -22,7 +22,7 @@ OPTIONS\n \tremote side, if it is not found on your $PATH. Some\n \tinstallations of sshd ignores the user's environment\n \tsetup scripts for login shells (e.g. .bash_profile) and\n-\tyour privately installed GIT may not be found on the system\n+\tyour privately installed git may not be found on the system\n \tdefault $PATH.  Another workaround suggested is to set\n \tup your $PATH in \".bashrc\", but this flag is for people\n \twho do not want to pay the overhead for non-interactive\ndiff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt\n--- a/Documentation/git-rev-parse.txt\n+++ b/Documentation/git-rev-parse.txt\n@@ -91,7 +91,7 @@ what is called an 'extended SHA1' syntax\n * A symbolic ref name.  E.g. 'master' typically means the commit\n   object referenced by $GIT_DIR/refs/heads/master.  If you\n   happen to have both heads/master and tags/master, you can\n-  explicitly say 'heads/master' to tell GIT which one you mean.\n+  explicitly say 'heads/master' to tell git which one you mean.\n \n * A suffix '^' to a revision parameter means the first parent of\n   that commit object.  '^<n>' means the <n>th parent (i.e.\ndiff --git a/Documentation/git-show-index.txt b/Documentation/git-show-index.txt\n--- a/Documentation/git-show-index.txt\n+++ b/Documentation/git-show-index.txt\n@@ -13,7 +13,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Reads given idx file for packed GIT archive created with\n+Reads given idx file for packed git archive created with\n git-pack-objects command, and dumps its contents.\n \n The information it outputs is subset of what you can get from\ndiff --git a/Documentation/git-verify-pack.txt b/Documentation/git-verify-pack.txt\n--- a/Documentation/git-verify-pack.txt\n+++ b/Documentation/git-verify-pack.txt\n@@ -3,7 +3,7 @@ git-verify-pack(1)\n \n NAME\n ----\n-git-verify-pack - Validate packed GIT archive files.\n+git-verify-pack - Validate packed git archive files.\n \n \n SYNOPSIS\n@@ -13,7 +13,7 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-Reads given idx file for packed GIT archive created with\n+Reads given idx file for packed git archive created with\n git-pack-objects command and verifies idx file and the\n corresponding pack file.\n \ndiff --git a/Documentation/git.txt b/Documentation/git.txt\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -146,7 +146,7 @@ gitlink:git-var[1]::\n \tDisplays a git logical variable\n \n gitlink:git-verify-pack[1]::\n-\tValidates packed GIT archive files\n+\tValidates packed git archive files\n \n The interrogate commands may create files - and you can force them to\n touch the working file set - but in general they don't\n@@ -163,11 +163,11 @@ gitlink:git-fetch-pack[1]::\n \tUpdates from a remote repository.\n \n gitlink:git-http-fetch[1]::\n-\tDownloads a remote GIT repository via HTTP\n+\tDownloads a remote git repository via HTTP\n \tPreviously this command was known as git-http-pull.\n \n gitlink:git-local-fetch[1]::\n-\tDuplicates another GIT repository on a local system\n+\tDuplicates another git repository on a local system\n \tPreviously this command was known as git-local-pull.\n \n gitlink:git-peek-remote[1]::\n@@ -322,7 +322,7 @@ gitlink:git-archimport[1]::\n \tPreviously this command was known as git-archimport-script.\n \n gitlink:git-convert-objects[1]::\n-\tConverts old-style GIT repository\n+\tConverts old-style git repository\n \tPreviously this command was known as git-convert-cache.\n \n gitlink:git-cvsimport[1]::\n@@ -360,7 +360,7 @@ gitlink:git-count-objects[1]::\n \tPreviously this command was known as git-count-objects-script.\n \n gitlink:git-daemon[1]::\n-\tA really simple server for GIT repositories.\n+\tA really simple server for git repositories.\n \n gitlink:git-get-tar-commit-id[1]::\n \tExtract commit ID from an archive created using git-tar-tree.\ndiff --git a/Documentation/glossary.txt b/Documentation/glossary.txt\n--- a/Documentation/glossary.txt\n+++ b/Documentation/glossary.txt\n@@ -1,5 +1,5 @@\n object::\n-\tThe unit of storage in GIT. It is uniquely identified by\n+\tThe unit of storage in git. It is uniquely identified by\n \tthe SHA1 of its contents. Consequently, an object can not\n \tbe changed.\n \ndiff --git a/Documentation/hooks.txt b/Documentation/hooks.txt\n--- a/Documentation/hooks.txt\n+++ b/Documentation/hooks.txt\n@@ -1,4 +1,4 @@\n-Hooks used by GIT\n+Hooks used by git\n =================\n \n Hooks are little scripts you can place in `$GIT_DIR/hooks`\ndiff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt\n--- a/Documentation/pull-fetch-param.txt\n+++ b/Documentation/pull-fetch-param.txt\n@@ -6,7 +6,7 @@\n ===============================================================\n - Rsync URL:\t\trsync://remote.machine/path/to/repo.git/\n - HTTP(s) URL:\t\thttp://remote.machine/path/to/repo.git/\n-- GIT URL:\t\tgit://remote.machine/path/to/repo.git/\n+- git URL:\t\tgit://remote.machine/path/to/repo.git/\n \t\t\tor remote.machine:/path/to/repo.git/\n - Local directory:\t/path/to/repo.git/\n ===============================================================\ndiff --git a/Documentation/repository-layout.txt b/Documentation/repository-layout.txt\n--- a/Documentation/repository-layout.txt\n+++ b/Documentation/repository-layout.txt\n@@ -1,4 +1,4 @@\n-GIT repository layout\n+git repository layout\n =====================\n \n You may find these things in your git repository (`.git`\n@@ -119,7 +119,7 @@ info/grafts::\n info/exclude::\n \tThis file, by convention among Porcelains, stores the\n \texclude pattern list.  `git status` looks at it, but\n-\totherwise it is not looked at by any of the core GIT\n+\totherwise it is not looked at by any of the core git\n \tcommands.\n \n remotes::\ndiff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt\n--- a/Documentation/tutorial.txt\n+++ b/Documentation/tutorial.txt\n@@ -160,7 +160,7 @@ you'll have to use the object name, not \n \tgit-cat-file -t 557db03de997c86a4a028e1ebd3a1ceb225be238\n \n where the `-t` tells `git-cat-file` to tell you what the \"type\" of the\n-object is. Git will tell you that you have a \"blob\" object (ie just a\n+object is. git will tell you that you have a \"blob\" object (ie just a\n regular file), and you can see the contents with\n \n \tgit-cat-file \"blob\" 557db03\n@@ -377,7 +377,7 @@ come from the working tree or not.\n \n This is not hard to understand, as soon as you realize that git simply\n never knows (or cares) about files that it is not told about\n-explicitly. Git will never go *looking* for files to compare, it\n+explicitly. git will never go *looking* for files to compare, it\n expects you to tell it what the files are, and that's what the index\n is there for.\n ================\n@@ -543,7 +543,7 @@ name for the state at that point.\n Copying repositories\n --------------------\n \n-Git repositories are normally totally self-sufficient, and it's worth noting\n+git repositories are normally totally self-sufficient, and it's worth noting\n that unlike CVS, for example, there is no separate notion of\n \"repository\" and \"working tree\". A git repository normally *is* the\n working tree, with the local git information hidden in the `.git`\n@@ -950,7 +950,7 @@ This transport is the same as SSH transp\n both ends on the local machine instead of running other end on\n the remote machine via `ssh`.\n \n-GIT Native::\n+git Native::\n \t`git://remote.machine/path/to/repo.git/`\n +\n This transport was designed for anonymous downloading.  Like SSH\n@@ -971,13 +971,13 @@ necessary objects.  Because of this beha\n sometimes also called 'commit walkers'.\n +\n The 'commit walkers' are sometimes also called 'dumb\n-transports', because they do not require any GIT aware smart\n-server like GIT Native transport does.  Any stock HTTP server\n+transports', because they do not require any git aware smart\n+server like git Native transport does.  Any stock HTTP server\n would suffice.\n +\n There are (confusingly enough) `git-ssh-fetch` and `git-ssh-upload`\n programs, which are 'commit walkers'; they outlived their\n-usefulness when GIT Native and SSH transports were introduced,\n+usefulness when git Native and SSH transports were introduced,\n and not used by `git pull` or `git push` scripts.\n \n Once you fetch from the remote repository, you `resolve` that\n@@ -1081,7 +1081,7 @@ done only once.\n on the remote machine. The communication between the two over\n the network internally uses an SSH connection.\n \n-Your private repository's GIT directory is usually `.git`, but\n+Your private repository's git directory is usually `.git`, but\n your public repository is often named after the project name,\n i.e. `<project>.git`. Let's create such a public repository for\n project `my-git`. After logging into the remote machine, create\n@@ -1089,7 +1089,7 @@ an empty directory:\n \n \tmkdir my-git.git\n \n-Then, make that directory into a GIT repository by running\n+Then, make that directory into a git repository by running\n `git init-db`, but this time, since its name is not the usual\n `.git`, we do things slightly differently:\n \n"},{"id":"9947","messageId":"m3ll10iqm9.fsf@lugabout.cloos.reno.nv.us","threadId":"2064","inReplyTo":"1128979592.7097.38.camel@localhost","subject":"Re: [PATCH] Convert usage of GIT and Git into git","fromName":"James Cloos","fromEmail":"cloos@jhcloos.com","sentAt":"2005-10-11T05:12:30Z","receivedAt":"2005-10-11T05:12:30Z","isPatch":true,"sender":{"key":"cloos@jhcloos.com","avatar":"https://gravatar.com/avatar/ec9a05787d29afe41e243e4b60bd0e2f69d757688e8f0bfe5e78bc185a3e317f?d=mp&s=160"},"body":",----\n| -manager, and you'll thus be happy with almost anything else. Git,\n| +manager, and you'll thus be happy with almost anything else. git,\n`----\n\nAn initial majuscule should still be used at the start of a sentence, yes?\n\n-JimC\n-- \nJames H. Cloos, Jr. <cloos@jhcloos.com>\n"},{"id":"9951","messageId":"1129009946.7097.46.camel@localhost","threadId":"2064","inReplyTo":"m3ll10iqm9.fsf@lugabout.cloos.reno.nv.us","subject":"Re: [PATCH] Convert usage of GIT and Git into git","fromName":"Christian Meder","fromEmail":"chris@absolutegiganten.org","sentAt":"2005-10-11T05:52:25Z","receivedAt":"2005-10-11T05:52:25Z","isPatch":true,"sender":{"key":"chris@absolutegiganten.org","avatar":null},"body":"On Tue, 2005-10-11 at 01:12 -0400, James Cloos wrote:\n> ,----\n> | -manager, and you'll thus be happy with almost anything else. Git,\n> | +manager, and you'll thus be happy with almost anything else. git,\n> `----\n> \n> An initial majuscule should still be used at the start of a sentence, yes?\n\nPersonally I think that 'Git' looks ugly compared to 'git'. But that's\nthe call of Junio and/or Linus. I'll change the manpages accordingly.\n\n\n\t\t\t\tChristian\n-- \nChristian Meder, email: chris@absolutegiganten.org\n\nThe Way-Seeking Mind of a tenzo is actualized \nby rolling up your sleeves.\n\n                (Eihei Dogen Zenji)\n"},{"id":"9950","messageId":"94fc236b0510102327l5c8b8b7cw3e0c5e7eb232cc8@mail.gmail.com","threadId":"2064","inReplyTo":"m3ll10iqm9.fsf@lugabout.cloos.reno.nv.us","subject":"Re: [PATCH] Convert usage of GIT and Git into git","fromName":"Adrien Beau","fromEmail":"adrienbeau@gmail.com","sentAt":"2005-10-11T06:27:40Z","receivedAt":"2005-10-11T06:27:40Z","isPatch":true,"sender":{"key":"adrienbeau@gmail.com","avatar":null},"body":"On 10/11/05, James Cloos <cloos@jhcloos.com> wrote:\n> ,----\n> | -manager, and you'll thus be happy with almost anything else. Git,\n> | +manager, and you'll thus be happy with almost anything else. git,\n> `----\n>\n> An initial majuscule should still be used at the start of a sentence, yes?\n\nI do think so.\n"}]}