Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-21 Thread David Greaves
We've decided to go for the individual scripts directly. :-) Just to clarify - individual scripts or $0 name handling? I kinda like one big script - also means we don't need to 'install' it to get access to Cogito.pm... Unfortunately, you didn't send the attachments inline, so I can't comment on

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-20 Thread Petr Baudis
Dear diary, on Tue, Apr 19, 2005 at 09:04:16PM CEST, I got a letter where David Greaves <[EMAIL PROTECTED]> told me that... > I don't love the 'require gitadd.pl' but it's a gradual start... I hate it, for one. ;-) > Cogito.pm seems to be a good place for the library stuff. Sounds sensible. > g

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-19 Thread David Greaves
Steven Cole wrote: Speaking of "I think", the name "cogito" was suggested for the SCM layer, but IIRC Linus suggested staying with just plain git. Petr suggested tig, perhaps because it looks at git from another point of view. I haven't read _all_ the mails - I thought cogito was kinda selected and

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-19 Thread Steven Cole
David Greaves wrote: Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 07:35:15PM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... I've been working on git.pl and getting help working nicely things to try: git.pl help git.pl add git.pl add --help git.pl add --man git.

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-19 Thread David Greaves
Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 07:35:15PM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... I've been working on git.pl and getting help working nicely things to try: git.pl help git.pl add git.pl add --help git.pl add --man git.pl help add The main

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-19 Thread Petr Baudis
Dear diary, on Tue, Apr 19, 2005 at 07:35:15PM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... > Example: ..snip a perfect-looking example.. > - > Speaking of 'git diff', I ran that before applying the following patch, > and got a diff starting thusly: > > --- /

Re: [PATCH] Add help details to git help command. (This time with Perl)

2005-04-19 Thread Steven Cole
Petr Baudis wrote: Dear diary, on Mon, Apr 18, 2005 at 06:42:26AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... [snippage] This patch will provide the comment lines in the shell script associated with the command, cleaned up a bit for presentation. BUGS: This will also

Re: [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

2005-04-19 Thread Petr Baudis
Dear diary, on Tue, Apr 19, 2005 at 04:41:34PM CEST, I got a letter where David Greaves <[EMAIL PROTECTED]> told me that... > If Petr wants the top comment to be extracted by help then maybe a > bottom comment block could contain the more complete text? > I *really* think that the user docs should

Re: [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

2005-04-19 Thread Steven Cole
David Greaves wrote: Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 03:40:54AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... Here is perhaps a better way to provide detailed help for each git command. A command.help file for each command can be written in the s

Re: [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

2005-04-19 Thread David Greaves
Petr Baudis wrote: Dear diary, on Tue, Apr 19, 2005 at 03:40:54AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... Here is perhaps a better way to provide detailed help for each git command. A command.help file for each command can be written in the style of a man page.

Re: [RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

2005-04-18 Thread Petr Baudis
Dear diary, on Tue, Apr 19, 2005 at 03:40:54AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... > Here is perhaps a better way to provide detailed help for each > git command. A command.help file for each command can be > written in the style of a man page. I don't like

[RFC] Another way to provide help details. (was Re: [PATCH] Add help details to git help command.)

2005-04-18 Thread Steven Cole
On Monday 18 April 2005 10:59 am, Steven Cole wrote: > Petr Baudis wrote: > > Dear diary, on Mon, Apr 18, 2005 at 06:42:26AM CEST, I got a letter > > where Steven Cole <[EMAIL PROTECTED]> told me that... > [snippage] > > > >>This patch will provide the comment lines in the shell script associated

Re: [PATCH] Add help details to git help command.

2005-04-18 Thread Steven Cole
Petr Baudis wrote: Dear diary, on Mon, Apr 18, 2005 at 06:42:26AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... [snippage] This patch will provide the comment lines in the shell script associated with the command, cleaned up a bit for presentation. BUGS: This will also

Re: [PATCH] Add help details to git help command.

2005-04-18 Thread Petr Baudis
Dear diary, on Mon, Apr 18, 2005 at 06:42:26AM CEST, I got a letter where Steven Cole <[EMAIL PROTECTED]> told me that... > There's a patch at the bottom of this, so please look at that first before > my reading my whining immediately below. > > I'm having some troubles with git pull, so this is j

[PATCH] Add help details to git help command.

2005-04-17 Thread Steven Cole
There's a patch at the bottom of this, so please look at that first before my reading my whining immediately below. I'm having some troubles with git pull, so this is just an ordinary diff. Otherwise, I would have used the in-house diff command. patch: Only garbage was found in the patch in