Re: [PATCH] Add documentation on how to integrate commands.

2012-11-25 Thread Eric S. Raymond
Junio C Hamano : > As the first sentence in this paragraph does not make it clear > enough that you are defining a new term "git execution directory", > "execution directory" here may be misleading and can easily be > mistaken as if we look something in the directory where the user > runs "git" in.

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-25 Thread Junio C Hamano
e...@thyrsus.com (Eric S. Raymond) writes: > --- Sign off? > Documentation/CommandIntegration | 69 > ++ > 1 file changed, 69 insertions(+) > create mode 100644 Documentation/CommandIntegration > > diff --git a/Documentation/CommandIntegration > b/Docume

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-25 Thread Eric S. Raymond
Michael Haggerty : > I think that here a reference to the file t/README would help (and > perhaps make part of your text redundant). Thank you, done. -- http://www.catb.org/~esr/";>Eric S. Raymond -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a m

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-24 Thread Michael Haggerty
On 11/24/2012 01:23 PM, Eric S. Raymond wrote: > --- > Documentation/CommandIntegration | 69 > ++ > 1 file changed, 69 insertions(+) > create mode 100644 Documentation/CommandIntegration > > diff --git a/Documentation/CommandIntegration > b/Documentation/

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-24 Thread Eric S. Raymond
Working on my revised patch... Pete Wyckoff : > Nice start. A few other details; I recently did this for git-p4 > (python). > > .gitignore: ignore the auto-generated script, e.g. when > git-foo.py is built into git-foo. Added: 3. If your command is implemented in an interpreted language wi

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-24 Thread Eric S. Raymond
Pete Wyckoff : > Nice start. A few other details; I recently did this for git-p4 > (python). > > .gitignore: ignore the auto-generated script, e.g. when > git-foo.py is built into git-foo. > > INSTALL: note language requirements if odd (see python section) > > command-list.txt: categorization o

Re: [PATCH] Add documentation on how to integrate commands.

2012-11-24 Thread Pete Wyckoff
e...@thyrsus.com wrote on Sat, 24 Nov 2012 07:23 -0500: > +== Integrating a command == > + > +Here are the things you need to do when you want to merge a new > +subcommand into the git tree. > + > +1. Append your command name to one of the variables BUILTIN_OBJS, > +EXTRA_PROGRAMS, SCRIPT_SH, SCRI

[PATCH] Add documentation on how to integrate commands.

2012-11-24 Thread Eric S. Raymond
--- Documentation/CommandIntegration | 69 ++ 1 file changed, 69 insertions(+) create mode 100644 Documentation/CommandIntegration diff --git a/Documentation/CommandIntegration b/Documentation/CommandIntegration new file mode 100644 index 000..be248f7 --