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

[PATCH] add gitignore entry to description about how to write a builtin

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Aug 3, 2011, 18:06 UTC
Message-ID
<20110803180617.GB13057@sandbox-rc>

If the author forgets the gitignore entry the built result will show up as new file in the git working directory.

Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
---
 Documentation/technical/api-builtin.txt |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/technical/api-builtin.txt b/Documentation/technical/api-builtin.txt
index 5cb2b05..b0cafe8 100644
--- a/Documentation/technical/api-builtin.txt
+++ b/Documentation/technical/api-builtin.txt
@@ -49,6 +49,8 @@ Additionally, if `foo` is a new command, there are 3 more things to do:
 
 . Add an entry for `git-foo` to `command-list.txt`.
 
+. Add an entry for `/git-foo` to `.gitignore`.
+
 
 How a built-in is called
 ------------------------

-- 
1.7.6.353.g02057.dirty
Message 1 of 1 in “add gitignore entry to description about how to write a builtin”
  1. add gitignore entry to description about how to write a builtinHeiko Voigt, Aug 3, 2011

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.