mirror of
https://github.com/tj/git-extras.git
synced 2026-09-10 07:26:17 -04:00
Spelling fixes for the roon file and html files
This commit is contained in:
Ye Lin Aung
parent
3ae8d22637
commit
f0a8b9e17e
|
|
@ -16,7 +16,7 @@
|
|||
Generates a changelog from git(1) tags (annotated or lightweight) and commit messages\. Existing changelog files with filenames that begin with \fIChange\fR or \fIHistory\fR will be identified automatically with a case insensitive match pattern and existing content will be appended to the new output generated\-\-this behavior can be disabled by specifying the prune option (\-p|\-\-prune\-old)\. The generated file will be opened in \fB$EDITOR\fR when set\.
|
||||
.
|
||||
.P
|
||||
If no tags exist, then all commits are output; if tags exist, then only the most\-recent commits are output up to the last identified tag\. This behavior can be changed by specifing one or both of the range options (\-f|\-\-final\-tag and \-s|\-\-start\-tag)\.
|
||||
If no tags exist, then all commits are output; if tags exist, then only the most\-recent commits are output up to the last identified tag\. This behavior can be changed by specifying one or both of the range options (\-f|\-\-final\-tag and \-s|\-\-start\-tag)\.
|
||||
.
|
||||
.SH "OPTIONS"
|
||||
<file>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@
|
|||
|
||||
<p> Generates a changelog from <span class="man-ref">git<span class="s">(1)</span></span> tags (annotated or lightweight) and commit messages. Existing changelog files with filenames that begin with <em>Change</em> or <em>History</em> will be identified automatically with a case insensitive match pattern and existing content will be appended to the new output generated--this behavior can be disabled by specifying the prune option (-p|--prune-old). The generated file will be opened in <strong>$EDITOR</strong> when set.</p>
|
||||
|
||||
<p> If no tags exist, then all commits are output; if tags exist, then only the most-recent commits are output up to the last identified tag. This behavior can be changed by specifing one or both of the range options (-f|--final-tag and -s|--start-tag).</p>
|
||||
<p> If no tags exist, then all commits are output; if tags exist, then only the most-recent commits are output up to the last identified tag. This behavior can be changed by specifying one or both of the range options (-f|--final-tag and -s|--start-tag).</p>
|
||||
|
||||
<h2 id="OPTIONS">OPTIONS</h2>
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ $ git chore finish chore\-123456
|
|||
.fi
|
||||
.
|
||||
.SH "AUTHOR"
|
||||
Written by Chris Hall <\fIchristopher\.k\.hall@gmail\.com\fR> from bug/feature/refactor comamnds originally written by Jesús Espino <\fIjespinog@gmail\.com\fR>
|
||||
Written by Chris Hall <\fIchristopher\.k\.hall@gmail\.com\fR> from bug/feature/refactor commands originally written by Jesús Espino <\fIjespinog@gmail\.com\fR>
|
||||
.
|
||||
.SH "REPORTING BUGS"
|
||||
<\fIhttps://github\.com/tj/git\-extras/issues\fR>
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ $ git chore finish chore-123456
|
|||
|
||||
<h2 id="AUTHOR">AUTHOR</h2>
|
||||
|
||||
<p>Written by Chris Hall <<a href="mailto:christopher.k.hall@gmail.com" data-bare-link="true">christopher.k.hall@gmail.com</a>> from bug/feature/refactor comamnds originally written by Jesús Espino <<a href="mailto:jespinog@gmail.com" data-bare-link="true">jespinog@gmail.com</a>></p>
|
||||
<p>Written by Chris Hall <<a href="mailto:christopher.k.hall@gmail.com" data-bare-link="true">christopher.k.hall@gmail.com</a>> from bug/feature/refactor commands originally written by Jesús Espino <<a href="mailto:jespinog@gmail.com" data-bare-link="true">jespinog@gmail.com</a>></p>
|
||||
|
||||
<h2 id="REPORTING-BUGS">REPORTING BUGS</h2>
|
||||
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ $ git guilt (1)
|
|||
spacewander ++++
|
||||
|
||||
(1) There is only one modified file and it is not staged\. The four
|
||||
plusses means that the file has four lines, all contributed by spacewander\.
|
||||
pluses means that the file has four lines, all contributed by spacewander\.
|
||||
.
|
||||
.fi
|
||||
.
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ If not specified, <until> will default to HEAD.</p>
|
|||
spacewander ++++
|
||||
|
||||
(1) There is only one modified file and it is not staged. The four
|
||||
plusses means that the file has four lines, all contributed by spacewander.
|
||||
pluses means that the file has four lines, all contributed by spacewander.
|
||||
</code></pre>
|
||||
|
||||
<p>Find blame delta between two commits:</p>
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ An optional prefix ! which negates the pattern; any matching file excluded by a
|
|||
If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory\. In other words, foo/ will match a directory foo and paths underneath it, but will not match a regular file or a symbolic link foo (this is consistent with the way how pathspec works in general in git)\.
|
||||
.
|
||||
.IP "\(bu" 4
|
||||
If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the \.gitignore file (relative to the toplevel of the work tree if not from a \.gitignore file)\.
|
||||
If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the \.gitignore file (relative to the top level of the work tree if not from a \.gitignore file)\.
|
||||
.
|
||||
.IP "\(bu" 4
|
||||
Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname\. For example, "Documentation/*\.html" matches "Documentation/git\.html" but not "Documentation/ppc/ppc\.html" or "tools/perf/Documentation/perf\.html"\.
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@
|
|||
<li><p>A line starting with # serves as a comment. For example, "# This is a comment"</p></li>
|
||||
<li><p>An optional prefix ! which negates the pattern; any matching file excluded by a previous pattern will become included again. If a negated pattern matches, this will override lower precedence patterns sources. To use an exclamation ! as command line argument it is best placed between single quotes ''. For example, '!src'</p></li>
|
||||
<li><p>If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory. In other words, foo/ will match a directory foo and paths underneath it, but will not match a regular file or a symbolic link foo (this is consistent with the way how pathspec works in general in git).</p></li>
|
||||
<li><p>If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the .gitignore file (relative to the toplevel of the work tree if not from a .gitignore file).</p></li>
|
||||
<li><p>If the pattern does not contain a slash /, git treats it as a shell glob pattern and checks for a match against the pathname relative to the location of the .gitignore file (relative to the top level of the work tree if not from a .gitignore file).</p></li>
|
||||
<li><p>Otherwise, git treats the pattern as a shell glob suitable for consumption by <span class="man-ref">fnmatch<span class="s">(3)</span></span> with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname. For example, "Documentation/*.html" matches "Documentation/git.html" but not "Documentation/ppc/ppc.html" or "tools/perf/Documentation/perf.html".</p></li>
|
||||
<li><p>A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".</p></li>
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Pattern format as described in the git manual
|
|||
|
||||
* Otherwise, git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname. For example, "Documentation/*.html" matches "Documentation/git.html" but not "Documentation/ppc/ppc.html" or "tools/perf/Documentation/perf.html".
|
||||
|
||||
* A leading slash matches the beginning of the path name. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
|
||||
* A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".
|
||||
|
||||
|
||||
## EXAMPLES
|
||||
|
|
|
|||
|
|
@ -10,10 +10,10 @@
|
|||
git obliterate <files\.\.\.> [\-\- <rev\-list options\.\.\.>]
|
||||
.
|
||||
.SH "DESCRIPTION"
|
||||
Completely remove some files from the repository, including past commits and tags\. WARNING! This command will rewirte the history similar to \fBgit rebase\fR(though it affects more)\. The rewritten history will have different object names for all the objects and will not converge with the original branch\. So \fBavoid using it on commits that you shared\fR\. And it will mess up stash, so \fBdon\'t have stash when you run \fBgit obliterate\fR\fR\.
|
||||
Completely remove some files from the repository, including past commits and tags\. WARNING! This command will rewrite the history similar to \fBgit rebase\fR(though it affects more)\. The rewritten history will have different object names for all the objects and will not converge with the original branch\. So \fBavoid using it on commits that you shared\fR\. And it will mess up stash, so \fBdon\'t have stash when you run \fBgit obliterate\fR\fR\.
|
||||
.
|
||||
.SH "OPTIONS"
|
||||
You can pass rev\-list options to indicate the range of commits affected\. Those options need to be seperated with \'\-\-\' before them\. Run \fBgit help rev\-list\fR to see the acceptable options\.
|
||||
You can pass rev\-list options to indicate the range of commits affected\. Those options need to be separated with \'\-\-\' before them\. Run \fBgit help rev\-list\fR to see the acceptable options\.
|
||||
.
|
||||
.SH "Examples"
|
||||
Remove \.secret from the repository:
|
||||
|
|
|
|||
|
|
@ -81,12 +81,12 @@
|
|||
<h2 id="DESCRIPTION">DESCRIPTION</h2>
|
||||
|
||||
<p>Completely remove some files from the repository, including past commits and tags.
|
||||
WARNING! This command will rewirte the history similar to <code>git rebase</code>(though it affects more). The rewritten history will have different object names for all the objects and will not converge with the original branch. So <strong>avoid using it on commits that you shared</strong>.
|
||||
WARNING! This command will rewrite the history similar to <code>git rebase</code>(though it affects more). The rewritten history will have different object names for all the objects and will not converge with the original branch. So <strong>avoid using it on commits that you shared</strong>.
|
||||
And it will mess up stash, so <strong>don't have stash when you run <code>git obliterate</code></strong>.</p>
|
||||
|
||||
<h2 id="OPTIONS">OPTIONS</h2>
|
||||
|
||||
<p>You can pass rev-list options to indicate the range of commits affected. Those options need to be seperated with '--' before them. Run <code>git help rev-list</code> to see the acceptable options.</p>
|
||||
<p>You can pass rev-list options to indicate the range of commits affected. Those options need to be separated with '--' before them. Run <code>git help rev-list</code> to see the acceptable options.</p>
|
||||
|
||||
<h2 id="Examples">Examples</h2>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
\fBgit\-pull\-request\fR [<target branch>]
|
||||
.
|
||||
.SH "DESCRIPTION"
|
||||
Create pull request for a project on GitHub via commandline\.
|
||||
Create pull request for a project on GitHub via command line\.
|
||||
.
|
||||
.P
|
||||
Uses the email from \fBgit config user\.email\fR to open the pull request\.
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@
|
|||
|
||||
<h2 id="DESCRIPTION">DESCRIPTION</h2>
|
||||
|
||||
<p>Create pull request for a project on GitHub via commandline.</p>
|
||||
<p>Create pull request for a project on GitHub via command line.</p>
|
||||
|
||||
<p>Uses the email from <code>git config user.email</code> to open the pull request.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@
|
|||
Lets you replace the author and/or committer identities in commits and tags\.
|
||||
.
|
||||
.P
|
||||
The command goes through all existing commits and tags in all local branches to selectively modify the identities present in those objects\. All the other informations such as dates, messages,\.\. are preserved\.
|
||||
The command goes through all existing commits and tags in all local branches to selectively modify the identities present in those objects\. All the other information such as dates, messages,\.\. are preserved\.
|
||||
.
|
||||
.P
|
||||
You can rewrite all the identities in the commits and tags objects by using the \-\-all flag, or only replace the identities whose email matches the value of the \-\-old\-email option\. It is also possible to limit the rewrite to a certain type of identity: the author or the committer identity\. By default, both of them are affected\.
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@
|
|||
|
||||
<p>Lets you replace the author and/or committer identities in commits and tags.</p>
|
||||
|
||||
<p>The command goes through all existing commits and tags in all local branches to selectively modify the identities present in those objects. All the other informations such as dates, messages,.. are preserved.</p>
|
||||
<p>The command goes through all existing commits and tags in all local branches to selectively modify the identities present in those objects. All the other information such as dates, messages,.. are preserved.</p>
|
||||
|
||||
<p>You can rewrite all the identities in the commits and tags objects by using the --all flag, or only replace the identities whose email matches the value of the --old-email option. It is also possible to limit the rewrite to a certain type of identity: the author or the committer identity. By default, both of them are affected.<br />
|
||||
For each of those identities to update, the command will replace the name and/or email with the new correct values as defined via the options. If the new identity name to set is not defined, the current one will be kept (and vice-versa with the email).</p>
|
||||
|
|
|
|||
Loading…
Reference in a new issue