Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Add some missing commands to the git.txt commands list
Date: Wed, 26 Oct 2005 00:03:21 +0200	[thread overview]
Message-ID: <20051025220321.GJ22079@pasky.or.cz> (raw)
In-Reply-To: <7vsluph6vx.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Tue, Oct 25, 2005 at 06:57:06PM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> Also we need a link to this in either Ancillary (in which
> subsection I am not sure of, though) or Synching repository
> section of git.txt.  I think we already lack links to a couple
> of recent commands there, so somebody needs to do another sweep
> of git.txt to make sure everything is listed.

for i in `l Documentation/*.txt | cut -d / -f 2 | cut -d . -f 1`; do
grep -q $i Documentation/git.txt || echo $i; done

But really, the more you have autogenerated, the better and more
consistent things are. In Cogito, I have all the documentation (usage
strings, synopsis, description, ...) at a _single_ place and everything
else (from command lists to various views of the docs) is autogenerated,
and it's a great help at making things complete and consistent. Also,
since it's inside of the code, people actually tend to remember to
update (and write in the first place) the documentation.


BTW, as of now, it appears that only the commands git-findtags and
git-fmt-merge-msg are undocumented.

---

[PATCH] Add some missing commands to the git.txt commands list

Signed-off-by: Petr Baudis <pasky@suse.cz>
---

 Documentation/git.txt |   18 ++++++++++++++++++
 1 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/Documentation/git.txt b/Documentation/git.txt
index 769054b..054f091 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -209,6 +209,9 @@ gitlink:git-add[1]::
 	Add paths to the index file.
 	Previously this command was known as git-add-script.
 
+gitlink:git-am[1]::
+	Apply patches from a mailbox, but cooler.
+
 gitlink:git-applymbox[1]::
 	Apply patches from a mailbox.
 
@@ -262,6 +265,9 @@ gitlink:git-ls-remote[1]::
 gitlink:git-merge[1]::
 	Grand unified merge driver.
 
+gitlink:git-mv[1]::
+	Move or rename a file, a directory, or a symlink.
+
 gitlink:git-octopus[1]::
 	Merge more than two commits.
 	Previously this command was known as git-octopus-script.
@@ -347,6 +353,9 @@ gitlink:git-relink[1]::
 	Hardlink common objects in local repositories.
 	Previously this command was known as git-relink-script.
 
+gitlink:git-svnimport[1]::
+	Import a SVN repository into git.
+
 gitlink:git-sh-setup[1]::
 	Common git shell script setup code.
 	Previously this command was known as git-sh-setup-script.
@@ -355,9 +364,15 @@ gitlink:git-tag[1]::
 	An example script to create a tag object signed with GPG
 	Previously this command was known as git-tag-script.
 
+gitlink:git-update-ref[1]::
+	Update the object name stored in a ref safely.
+
 
 Interrogators:
 
+gitlink:git-check-ref-format[1]::
+	Make sure ref name is well formed.
+
 gitlink:git-cherry[1]::
 	Find commits not merged upstream.
 
@@ -395,6 +410,9 @@ gitlink:git-send-email[1]::
 	Send patch e-mails out of "format-patch --mbox" output.
 	Previously this command was known as git-send-email-script.
 
+gitlink:git-symbolic-refs[1]::
+	Read and modify symbolic refs.
+
 gitlink:git-stripspace[1]::
 	Filter out empty lines.
 

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

      parent reply	other threads:[~2005-10-25 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25  9:09 [PATCH] Documentation for git-shell Petr Baudis
     [not found] ` <7vsluph6vx.fsf@assigned-by-dhcp.cox.net>
2005-10-25 21:43   ` Petr Baudis
2005-10-25 22:03   ` Petr Baudis [this message]

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=20051025220321.GJ22079@pasky.or.cz \
    --to=pasky@ucw.cz \
    --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