From: Fredrik Kuivinen <freku045@student.liu.se>
To: git@vger.kernel.org
Cc: junkio@cox.net
Subject: [PATCH 0/3] Make the output of 'git' nicer
Date: Thu, 9 Mar 2006 17:17:22 +0100 [thread overview]
Message-ID: <20060309161722.GA4484@c165.ib.student.liu.se> (raw)
Hi,
This series makes the output of 'git' easier to read (IMHO). With this
patch the output will look like this:
Usage: git [--version] [--exec-path[=GIT_EXEC_PATH]] [--help] COMMAND [ ARGS ]
The most commonly used git commands are:
add Add files to the index file
apply Apply patch on a git index file and a work tree
bisect Find the change that introduced a bug
branch Create a new branch, or remove an old one
checkout Checkout and switch to a branch
cherry-pick Apply the change introduced by an existing commit
clone Clones a repository
commit Record your changes
diff Show changes between commits, commit and working tree, etc
fetch Download objects and a head from another repository
grep Print lines matching a pattern
init-db Creates an empty git repository
log Show commit logs
merge Grand Unified Merge Driver
mv Move or rename a file, directory or symlink
prune Prunes all unreachable objects from the object database
pull Pull and merge from another repository
push Update remote refs along with associated objects
rebase Rebase local commits to new upstream head
reset Reset current HEAD to the specified state
revert Revert an existing commit
rm Remove files from the working tree and from the index
show-branch Show branches and their commits
status Show working tree status
tag Create a tag object signed with GPG
verify-tag Check the GPG signature of tag
whatchanged Show logs with difference each commit introduces
(use 'git help -a' to get a list of all installed git commands)
- Fredrik
next reply other threads:[~2006-03-09 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 16:17 Fredrik Kuivinen [this message]
2006-03-09 16:24 ` [PATCH 1/3] Nicer output from 'git' Fredrik Kuivinen
2006-03-09 17:14 ` Jan-Benedict Glaw
2006-03-09 16:24 ` [PATCH 2/3] Fix some inconsistencies in the docs Fredrik Kuivinen
2006-03-09 16:24 ` [PATCH 3/3] Remove trailing dot after short description Fredrik Kuivinen
2006-03-09 17:32 ` [PATCH 0/3] Make the output of 'git' nicer Ryan Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060309161722.GA4484@c165.ib.student.liu.se \
--to=freku045@student.liu.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).