git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 25/27] Documentation: Spelling fixes

From
Hhorst.h.von.brand@inf.utfsm.cl <horst.h.von.brand@inf.utfsm.cl>
Date
Jun 3, 2006, 20:27 UTC
Message-ID
<32989.2865186141$1149366554@news.gmane.org>
In-Reply-To
<11493665112903-git-send-email->
From: Horst H. von Brand <vonbrand@inf.utfsm.cl>
Signed-off-by: Horst H. von Brand <vonbrand@inf.utfsm.cl>
---
 Documentation/hooks.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/hooks.txt b/Documentation/hooks.txt
index 3824a95..e853b93 100644
--- a/Documentation/hooks.txt
+++ b/Documentation/hooks.txt
@@ -100,7 +100,7 @@ update
 This hook is invoked by `git-receive-pack` on the remote repository,
 which is happens when a `git push` is done on a local repository.
 Just before updating the ref on the remote repository, the update hook
-is invoked.  It's exit status determins the success or failure of
+is invoked.  It's exit status determines the success or failure of
 the ref update.
 
 The hook executes once for each ref to be updated, and takes
@@ -151,7 +151,7 @@ so it is a poor place to do log old..new
 
 The default post-update hook, when enabled, runs
 `git-update-server-info` to keep the information used by dumb
-transports (eg, http) up-to-date.  If you are publishing
+transports (e.g.,, http) up-to-date.  If you are publishing
 a git repository that is accessible via http, you should
 probably enable this hook.
 
-- 
1.3.3.g86f7
Previous: horst.h.von.brand@inf.utfsm.clNext: horst.h.von.brand@inf.utfsm.cl
Message 24 of 27 in “Documentation: Spelling fixes”
  1. 2/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  2. 3/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  3. 4/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  4. 5/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  5. 6/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  6. 7/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  7. 8/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  8. 9/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  9. 10/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  10. 11/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  11. 12/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  12. 13/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  13. 14/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  14. 15/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  15. 16/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  16. 17/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  17. 18/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  18. 19/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  19. 20/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  20. 21/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  21. 22/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  22. 23/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  23. 24/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  24. 25/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  25. 26/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  26. 27/27 Documentation: Spelling fixeshorst.h.von.brand@inf.utfsm.cl, Jun 3, 2006
  27. Ben CliffordJun 4, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.