[PATCH v4 3/3] git-help.txt: document "git help cmd" vs "git cmd --help" for aliases

This documents the existing behaviour of "git help cmd" when cmd is an alias, as well as providing a hint to use the "git cmd --help" form to be taken directly to the man page for the aliased command. Signed-off-by: Rasmus Villemoes --- Documentation/git-help.txt | 4 +++

[PATCH v3 3/3] git-help.txt: document "git help cmd" vs "git cmd --help" for aliases

This documents the existing behaviour of "git help cmd" when cmd is an alias, as well as providing a hint to use the "git cmd --help" form to be taken directly to the man page for the aliased command. Signed-off-by: Rasmus Villemoes --- Documentation/git-help.txt | 4 +++

Re: [PATCH v2 3/3] git-help.txt: document "git help cmd" vs "git cmd --help" for aliases

On 2018-10-03 04:18, Jeff King wrote: > On Mon, Oct 01, 2018 at 01:21:07PM +0200, Rasmus Villemoes wrote: > >> >> +If an alias is given, git prints a note explaining what it is an alias >> +for on standard output. To get the manual page for the aliased >> +command, use `git COMMAND --help`. >

Re: [PATCH v2 3/3] git-help.txt: document "git help cmd" vs "git cmd --help" for aliases

On Mon, Oct 01, 2018 at 01:21:07PM +0200, Rasmus Villemoes wrote: > This documents the existing behaviour of "git help cmd" when cmd is an > alias, as well as providing a hint to use the "git cmd --help" form to > be taken directly to the man page for the aliased

[PATCH v2 3/3] git-help.txt: document "git help cmd" vs "git cmd --help" for aliases

This documents the existing behaviour of "git help cmd" when cmd is an alias, as well as providing a hint to use the "git cmd --help" form to be taken directly to the man page for the aliased command. Signed-off-by: Rasmus Villemoes --- Documentation/git-help.txt | 4 +++

Re: [PATCH] git help: promote 'git help -av'

On Fri, Sep 28, 2018 at 09:30:51AM -0700, Junio C Hamano wrote: > Taylor Blau writes: > > > On Wed, Sep 26, 2018 at 10:28:31AM -0700, Junio C Hamano wrote: > >> Duy Nguyen writes: > >> > >> > Here's the patch that adds that external commands and aliases > >> > sections. I feel that external

Re: [PATCH] git help: promote 'git help -av'

Taylor Blau writes: > On Wed, Sep 26, 2018 at 10:28:31AM -0700, Junio C Hamano wrote: >> Duy Nguyen writes: >> >> > Here's the patch that adds that external commands and aliases >> > sections. I feel that external commands section is definitely good to >> > have even if we don't replace "help

Re: [PATCH] git help: promote 'git help -av'

On Wed, Sep 26, 2018 at 10:28:31AM -0700, Junio C Hamano wrote: > Duy Nguyen writes: > > > Here's the patch that adds that external commands and aliases > > sections. I feel that external commands section is definitely good to > > have even if we don't replace "help -a". Aliases are more > >

Re: [PATCH] git help: promote 'git help -av'

Duy Nguyen writes: > Here's the patch that adds that external commands and aliases > sections. I feel that external commands section is definitely good to > have even if we don't replace "help -a". Aliases are more > subjective... I didn't apply this (so I didn't try running it), but a quick

Re: [PATCH] git help: promote 'git help -av'

Duy Nguyen writes: > -v was recently added just for the new "help -a" in May 2018. I think > it's ok to get rid of it. Memory muscles probably take a couple more > months to kick in. If it is not hurting, keeping it lets people say "--no-verbose" to get a less verbose output to help those who

Re: [PATCH] git help: promote 'git help -av'

print command description")), > > OPT_END(), > > }; > > Would we want to continue respecting "-v" as a noop? I admit I did not > even know it existed until this thread, but if people have trained > themselves to run "git help -av", we should

Re: [PATCH] git help: promote 'git help -av'

AT_INFO), > - OPT__VERBOSE(, N_("print command description")), > OPT_END(), > }; Would we want to continue respecting "-v" as a noop? I admit I did not even know it existed until this thread, but if people have trained themselves to run "git help -av", we should probably continue to give them this output. -Peff

Re: [PATCH] git help: promote 'git help -av'

st = data; + + if (skip_prefix(var, "alias.", )) + string_list_append(list, var)->util = xstrdup(value); + + return 0; +} + void list_all_cmds_help(void) { - print_cmd_by_category(main_categories); + struct string_list others = STRING_LIST_INIT_DUP; +

Re: [PATCH] git help: promote 'git help -av'

On Mon, Sep 24, 2018 at 10:58 PM Junio C Hamano wrote: > I personally find "help -av" a bit too loud to my taste than plain > "-a", and more importantly, I look at "help -a" primarily to check > the last section "avaialble from elsewhere on your $PATH" to find > things like "clang-format", which

Re: [PATCH] git help: promote 'git help -av'

(I think it was up to 2.17.x series, but do not quote me on that) have parsed "git help -a" output to obtain the list of commands. So such a change would impact those minority users who keep stale completion script in their $HOME/.bashrc without ever update it, thinking it is good enough.

Re: [PATCH] git help: promote 'git help -av'

On Mon, Sep 24, 2018 at 03:20:00PM -0500, Taylor Blau wrote: > On Mon, Sep 24, 2018 at 02:19:28PM -0400, Jeff King wrote: > > On Sat, Sep 22, 2018 at 07:47:07PM +0200, Nguyễn Thái Ngọc Duy wrote: > > > > > When you type "git help" (or just "git") you

Re: [PATCH] git help: promote 'git help -av'

On Mon, Sep 24, 2018 at 02:19:28PM -0400, Jeff King wrote: > On Sat, Sep 22, 2018 at 07:47:07PM +0200, Nguyễn Thái Ngọc Duy wrote: > > > When you type "git help" (or just "git") you are greeted with a list > > with commonly used commands and their short de

Re: [PATCH] git help: promote 'git help -av'

On Sat, Sep 22, 2018 at 07:47:07PM +0200, Nguyễn Thái Ngọc Duy wrote: > When you type "git help" (or just "git") you are greeted with a list > with commonly used commands and their short description and are > suggested to use "git help -a" or "git h

Re: [PATCH] git help: promote 'git help -av'

On Sat, Sep 22, 2018 at 9:29 PM Ævar Arnfjörð Bjarmason wrote: > > > On Sat, Sep 22 2018, Nguyễn Thái Ngọc Duy wrote: > > > When you type "git help" (or just "git") you are greeted with a list > > with commonly used commands and their short descri

Re: [PATCH] git help: promote 'git help -av'

On Sat, Sep 22 2018, Nguyễn Thái Ngọc Duy wrote: > When you type "git help" (or just "git") you are greeted with a list > with commonly used commands and their short description and are > suggested to use "git help -a" or "git help -g" for more d

[PATCH] git help: promote 'git help -av'

When you type "git help" (or just "git") you are greeted with a list with commonly used commands and their short description and are suggested to use "git help -a" or "git help -g" for more details. "git help -av" would be more friendly and inline

Re: Git Help !!!

Awesome, thanks! On Thu, 26 Jul 2018, 2:00 p.m. Eric Sunshine, wrote: > On Thu, Jul 26, 2018 at 1:01 AM Vishwas Kamath > wrote: > > I am unable to use Git (version 2.18 latest). Since i couldnt find any > help/support/contact email on https://git-scm.com and i couldnt find the > solution using

Re: Git Help !!!

On Thu, Jul 26, 2018 at 1:01 AM Vishwas Kamath wrote: > I am unable to use Git (version 2.18 latest). Since i couldnt find any > help/support/contact email on https://git-scm.com and i couldnt find the > solution using Google as well i am directly contacting you as i need to get > git working.

Fwd: Git Help !!!

Hi, I am unable to use Git (version 2.18 latest). Since i couldnt find any help/support/contact email on https://git-scm.com and i couldnt find the solution using Google as well i am directly contacting you as i need to get git working. Hope you can help me. please find attached an image file

Re: git help clone: questions

Am 07.03.2018 um 23:45 schrieb Junio C Hamano: > kalle writes: > >> Am 06.03.2018 um 02:36 schrieb Junio C Hamano: >>> kalle writes: >>> -In the explanation of the option --reference: shouldn't there be written '' instead of

Re: git help clone: questions

kalle writes: > Am 06.03.2018 um 02:36 schrieb Junio C Hamano: >> kalle writes: >> >>> -In the explanation of the option --reference: shouldn't there be >>> written '' instead of 'reference repository'? >> >> "Shouldn't X be Y?" is not an

Re: git help clone: questions

I wrote this, because when it is written about 'reference repository', I consider it not totally clear, which repository is meant, as the option '--reference ' only names one as . For reasons of clearness, I now propose writing "reference repository ". kalle Am 06.03.2018 um 02:36 schrieb Junio

Re: git help clone: questions

kalle writes: > -In the explanation of the option --reference: shouldn't there be > written '' instead of 'reference repository'? "Shouldn't X be Y?" is not an effective way to communicate; it solicits a "no, the current one is fine." without any explanation. If you

git help clone: questions

-In the explanation of the option --reference: shouldn't there be written '' instead of 'reference repository'? greetings, kalle

missing entries in "git help repository-layout"

while writing up a cheat sheet with a visual layout of .git for my students, i compared "git help repository-layout" to my git clone of the kernel source tree, and noted the following things are not mentioned in the repo layout help page -- i have no idea how complete that page i

Re: `git help svn` missing description of `propset`

with a patch. thank you, -Alfred On 6/7/16 1:08 PM, Eric Wong wrote: +Cc Alfred, David Joseph Pecoraro <pecor...@apple.com> wrote: `git help svn` does not mention `propset` but it does mention `proplist` and `propget`. This seems like an oversight. $ git he

Re: `git help svn` missing description of `propset`

+Cc Alfred, David Joseph Pecoraro <pecor...@apple.com> wrote: > `git help svn` does not mention `propset` but it does mention `proplist` and > `propget`. This seems like an oversight. > > > $ git help svn > ... > proplist >

`git help svn` missing description of `propset`

`git help svn` does not mention `propset` but it does mention `proplist` and `propget`. This seems like an oversight. $ git help svn ... proplist Lists the properties stored in the Subversion repository about a given file or directory. Use -r/--revision

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

"Philip Oakley" <philipoak...@iee.org> writes: >> The first step may be to teach a new subcommand to "git help" >> to show a list of these words, and then _git_help can use it to >> lazily compute the list just like __git_commands does. > > 'g

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

lly that we have to maintain this list to be in sync with the set of documents we offer. Wouldn't it make more sense to go in the direction of _removing_ this list of hardcoded words here? The first step may be to teach a new subcommand to "git help" to show a list of these words, and then

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

be in sync with the set of documents we offer. Wouldn't it make more sense to go in the direction of _removing_ this list of hardcoded words here? The first step may be to teach a new subcommand to "git help" to show a list of these words, and then _git_help can use it to lazily compute the

Re: [PATCH 1/2] completion: add option '--guides' to 'git help'

Ralf Thielow writes: > Signed-off-by: Ralf Thielow > --- > contrib/completion/git-completion.bash | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Sounds sensible. Thanks. > > diff --git a/contrib/completion/git-completion.bash >

[PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

Signed-off-by: Ralf Thielow --- contrib/completion/git-completion.bash | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index 70f4171..ffe6004 100644 ---

[PATCH 0/2] completion: git-help: add missing option and params

The bash completion is missing the option '--guides' for 'git-help' and some params you see there. Add them both. Ralf Thielow (2): completion: add option '--guides' to 'git help' completion: add 'revisions' and 'everyday' to 'git help' contrib/completion/git-completion.bash | 6 +++--- 1

[PATCH 1/2] completion: add option '--guides' to 'git help'

Signed-off-by: Ralf Thielow --- contrib/completion/git-completion.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index e3918c8..70f4171 100644 ---

Re: [PATCH v7 0/5] git help: group common commands by theme

Eric Sunshine sunsh...@sunshineco.com writes: rebased on 'next' (a2776d4) Something to keep in mind for the future: It's usually easier to manage preparatory cleanup patches by incorporating them into the series which needs/wants them rather than posting them as separate topics. That way,

RE: Git Help needed

: git@vger.kernel.org Subject: RE: Git Help needed Hi Brian, Thank you. Understood OpeSSL and vendor from your original message now. Thanks, Ravi. -Original Message- From: brian m. carlson [mailto:sand...@crustytoothpaste.net] Sent: Friday, August 01, 2014 5:00 PM To: Ravi Kiran Goud

Re: Git Help needed

On Tue, Oct 21, 2014 at 12:31:55PM +, ravikirangoud_palpano...@vfc.com wrote: Hi Brian, My Open SSL vendor is IBM. In fact I am using AIX OS from IBM. When we (Myself and Frank. Frank is cc'ed in this email) discussed with IBM team, they asked some details on what flag settings need to

Re: [PATCH v4 0/3] Make 'git help everyday' work

From: Junio C Hamano gits...@pobox.com Thanks. Looked alright from a cursory read; I tweaked s/10/-10/ where you gave examples of limiting output from git log before queuing. That was my mis-reading. I'd even noticed that it looked 'different' but just didn't see the leading '-' when checking

[PATCH v4 3/3] Make 'git help everyday' work

The Everyday GIT With 20 Commands Or So is not accessible via the Git help system. Move everyday.txt to giteveryday.txt so that git help everyday works, and create a new placeholder file everyday.html to refer people who follow existing URLs to the updated location. giteveryday.txt now formats

[PATCH v4 0/3] Make 'git help everyday' work

regularise OBSOLETE_HTML list building Make 'git help everyday' work Documentation/Makefile | 6 +- Documentation/everyday.txt | 413 - Documentation/everyday.txto| 9 + Documentation/git-push.txt | 2 +- Documentation

Re: [PATCH v4 0/3] Make 'git help everyday' work

Thanks. Looked alright from a cursory read; I tweaked s/10/-10/ where you gave examples of limiting output from git log before queuing. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH v3 3/3] Make 'git help everyday' work

The Everyday GIT With 20 Commands Or So is not accessible via the Git help system. Move everyday.txt to giteveryday.txt so that git help everyday works, and create a new placeholder file everyday.html to refer people who follow existing URLs to the updated location. giteveryday.txt now formats

[PATCH v3 0/3] Make 'git help everyday' work

Here's version three of my patches to make 'git help everyday' work. It's taken awhile. Previous patches at [1] and [2]. Junio has provided guidance on modernisation of the text, which has been integrated into patch 1. Patch 2 regularises the OBSOLETE_HTML method in the make file, in line

Git Help needed

library compatibility issue. The error is  OpenSSL version mismatch. Built agains 1000105f, you have 10bf fatal: Could not read from remote repository In order to get rid of this, I upgraded git to 1.9.0 GIT. But still it didn't work. The issue is still coming.  git help, version works.  When

Re: Git Help needed

. The error is OpenSSL version mismatch. Built agains 1000105f, you have 10bf fatal: Could not read from remote repository In order to get rid of this, I upgraded git to 1.9.0 GIT. But still it didn't work. The issue is still coming. git help, version works. When I tried directly pulling

Re: Git Help needed

On Fri, Aug 01, 2014 at 07:30:11PM +, ravikirangoud_palpano...@vfc.com wrote: Hi, I am writing below couple of questions. If it is not the right place to ask please ignore and suggest me what to do to get the help on these questions. 1) What version of SSL is supported by GIT 1.8.3 or

RE: Git Help needed

Subject: Re: Git Help needed This looks more like a packaging/build issue than a git issue. It looks like whomever built your version of git built it against a specific version of the OpenSSL library. You should probably contact the folks that built your binary and ask them to update and build

RE: Git Help needed

, August 01, 2014 4:05 PM To: Ravi Kiran Goud Palpanoori Cc: git@vger.kernel.org Subject: Re: Git Help needed On Fri, Aug 01, 2014 at 07:30:11PM +, ravikirangoud_palpano...@vfc.com wrote: Hi, I am writing below couple of questions. If it is not the right place to ask please ignore

Re: Git Help needed

On Fri, Aug 01, 2014 at 08:27:24PM +, ravikirangoud_palpano...@vfc.com wrote: Hi brian, Thanks for your quick reply. I downloaded git 1.9.0 from the site https://code.google.com/p/git-core/downloads/list. That URL is obsolete. Try https://www.kernel.org/pub/software/scm/git/ Google

RE: Git Help needed

Hi Brian, Thank you. Understood OpeSSL and vendor from your original message now. Thanks, Ravi. -Original Message- From: brian m. carlson [mailto:sand...@crustytoothpaste.net] Sent: Friday, August 01, 2014 5:00 PM To: Ravi Kiran Goud Palpanoori Cc: git@vger.kernel.org Subject: Re: Git

Re: [PATCH] help: include list of aliases in git-help --all

Joel Nothman joel.noth...@gmail.com writes: Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands in the main git directory and other $PATH directories. ... and why is this a good thing? Signed-off-by: Joel

Re: [PATCH] help: include list of aliases in git-help --all

On 26 February 2014 06:15, Junio C Hamano gits...@pobox.com wrote: Joel Nothman joel.noth...@gmail.com writes: Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands in the main git directory and other $PATH

Re: [PATCH] help: include list of aliases in git-help --all

Joel Nothman joel.noth...@gmail.com writes: arguments to git help. They are also like commands in that it is possible to forget their name, or whether they are defined on a particular workstation, and to hence want a listing. I did envision that it would be useful for the last case

Re: [PATCH] help: include list of aliases in git-help --all

On 26 February 2014 08:51, Junio C Hamano gits...@pobox.com wrote: Joel Nothman joel.noth...@gmail.com writes: arguments to git help. They are also like commands in that it is possible to forget their name, or whether they are defined on a particular workstation, and to hence want a listing

Re: [PATCH] help: include list of aliases in git-help --all

From: Joel Nothman joel.noth...@gmail.com On 26 February 2014 06:15, Junio C Hamano gits...@pobox.com wrote: Joel Nothman joel.noth...@gmail.com writes: Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands

Re: [PATCH] help: include list of aliases in git-help --all

Joel Nothman joel.noth...@gmail.com writes: Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands in the main git directory and other $PATH directories. Signed-off-by: Joel Nothman joel.nothman at gmail.com

[PATCH] help: include list of aliases in git-help --all

Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands in the main git directory and other $PATH directories. Signed-off-by: Joel Nothman joel.nothman at gmail.com --- Documentation/git-help.txt | 4 +-- builtin/help.c

Re: [PATCH] Provide a 'git help user-manual' route to the docbook

+ +gituser-manual - a link to the user-manual docbook + + +SYNOPSIS + +[verse] +'git help user-manual' + +link:user-manual.html[Git User's Manual] Is it just me, or is typing $ git help user-manual and not seeing the manual itself, but only a link you have to click

Re: [PATCH] Provide a 'git help user-manual' route to the docbook

(7) += + +NAME + +gituser-manual - a link to the user-manual docbook + + +SYNOPSIS + +[verse] +'git help user-manual' + +link:user-manual.html[Git User's Manual] Is it just me, or is typing $ git help user-manual and not seeing the manual itself, but only a link you

[PATCH] Provide a 'git help user-manual' route to the docbook

@@ +gituser-manual(7) += + +NAME + +gituser-manual - a link to the user-manual docbook + + +SYNOPSIS + +[verse] +'git help user-manual' + +link:user-manual.html[Git User's Manual] + +DESCRIPTION +--- +Git is a fast, scalable, distributed revision control system

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

within the git(1) section it came from, and a new release-notes(7) man page. With that set up the Documentation/Makefile would generate the man pages, with their appropriate links, which can be accessed via the 'git help' command. The big 'however' was that this would not actually include

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

From: Stefan Näwe stefan.na...@atlas-elektronik.com Am 16.01.2014 22:14, schrieb Philip Oakley: From: Stefan Näwe stefan.na...@atlas-elektronik.com [...] I'd really like to see 'git help relnotes' working as well... Stefan Stefan, Were you thinking that all the release notes would

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

Philip Oakley philipoak...@iee.org writes: Determining which is the current release note is possibly more problematic, which should be when making the documentation. Hmmm Why? You are already aware of the stale-notes section, no? Isn't the top one the latest? -- To unsubscribe from this

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

the latest? It's that the 'git help release-notes' would _include_ the latest release notes, not just link to them (which is what the stalenotes currently does). Or at least that was the idea. Trying to determine the latest version, and then include those release notes, and the subsequent

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

Philip Oakley philipoak...@iee.org writes: I already have a local patch that creates a stalenote.txt file, and includes that in a release-notes(7) man page, but it still leaves the actual release notes in a separate plain text file, linked from the man page, rather than being right at hand,

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

Am 16.01.2014 22:14, schrieb Philip Oakley: From: Stefan Näwe stefan.na...@atlas-elektronik.com [...] I'd really like to see 'git help relnotes' working as well... Stefan Stefan, Were you thinking that all the release notes would be quoted verbatim in the one long man page

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

From: Stefan Näwe stefan.na...@atlas-elektronik.com [...] I'd really like to see 'git help relnotes' working as well... Stefan Stefan, Were you thinking that all the release notes would be quoted verbatim in the one long man page? Or that it would be a set of links to each

[PATCH] Provide a 'git help user-manual' route to the docbook

@@ +gituser-manual(7) += + +NAME + +gituser-manual - a link to the user-manual docbook + + +SYNOPSIS + +[verse] +'git help user-manual' + +link:user-manual.html[Git User's Manual] + +DESCRIPTION +--- +Git is a fast, scalable, distributed revision control system

[PATCH v2] Make 'git help everyday' work

The Everyday GIT With 20 Commands Or So is not accessible via the Git help system. Fix that. Move everyday.txt to giteveryday.txt. Update giteveryday.txt to fit man page formatting. Add standard man page section titles. Also adjust anchor text markup for man page format. Add giteveryday

Re: [PATCH 0/6] Make 'git help everyday' work

about ensuring that the 'git help' command could access these extra extra guides that it currently misses. (Tt also misses the 'user-manual', which isn't a man page, but could have a link page to guide the seeker of truth between 'git help' and the actual user-manual) The only method I can see

Re: [PATCH 0/6] Make 'git help everyday' work

From: Junio C Hamano gits...@pobox.com I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. This was mainly about ensuring that the 'git help' command could access these extra extra guides

Re: [PATCH 0/6] Make 'git help everyday' work

changed over the past 8 years. Perhaps we should do that after reorganizing with something like this series. I'd really like to see 'git help relnotes' working as well... Stefan -- /dev/random says: Despite the high cost of living

Re: [PATCH 0/6] Make 'git help everyday' work

Philip Oakley philipoak...@iee.org writes: From: Junio C Hamano gits...@pobox.com I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. This was mainly about ensuring that the 'git help

Re: [PATCH 0/6] Make 'git help everyday' work

Hi, Philip Oakley wrote: The Everyday GIT With 20 Commands Or So guide is not accessible via the git help system. Fix that. Neat. :) Junio covered everything I'd want to say about patch 1/6. After fixing that, I'd suggest squashing all 6 patches into a single patch. They all are part

Re: [PATCH 0/6] Make 'git help everyday' work

about ensuring that the 'git help' command could access these extra extra guides that it currently misses. (Tt also misses the 'user-manual', which isn't a man page, but could have a link page to guide the seeker of truth between 'git help' and the actual user-manual) The only method I can see

[PATCH 0/6] Make 'git help everyday' work

The Everyday GIT With 20 Commands Or So guide is not accessible via the git help system. Fix that. The git everyday file does not use the appropriate filenaming convention for help files, and is not suitably formatted for display as a man page. First copy everyday.txt to giteveryday.txt Second

Re: [PATCH 0/6] Make 'git help everyday' work

I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. It may be overdue to refresh the suggested set of top 20 commands, as things have vastly changed over the past 8 years. Perhaps we should do

Re: Should git help respect the 'pager' setting?

of thing: how would we unset it after that? Perhaps something like execvpe(), passing in the environment as an argument? Running man is the last thing we do before exitting git help and exec_man_man() does seem to do execlp(), so I do not see it as an issue. Overriding PAGER might make sense

Should git help respect the 'pager' setting?

I have my global git config pager set to 'cat', but when I do a git help command, it still uses a pager. This is especially irksome in emacs shell buffers, where I am most of the time. I know I can do a M-x man - git-whatever, but wondered if this was a bug or user error. (git --no-pager help

Re: Should git help respect the 'pager' setting?

Michael Campbell michael.campb...@gmail.com writes: I have my global git config pager set to 'cat', but when I do a git help command, it still uses a pager. This is especially irksome in emacs shell buffers, where I am most of the time. I know I can do a M-x man - git-whatever, but wondered

Re: Should git help respect the 'pager' setting?

is there no option for Emacs man corresponding to Emacs woman? I guess because no one implemented it ;-). I personally run M-x git-foo RET, and never run git help. M-x man git-foo RET, you mean? Yes, sorry. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send

Re: Should git help respect the 'pager' setting?

Matthieu Moy wrote: I find it a bit weird that Git sets the configuration for external commands, but it may make sense. No strong opinion here. I don't mean a setenv() kind of thing: how would we unset it after that? Perhaps something like execvpe(), passing in the environment as an argument?

Re: Should git help respect the 'pager' setting?

man pages - invoking man through git help shouldn't cause it to behave differently in this case. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH V3 1/5] Show help: -a and -g option, and 'git help concept' usage.

Prepare for the addition of the -g --guides option to git help and show that help is available for both concept guides, and commands. Signed-off-by: Philip Oakley philipoak...@iee.org --- git.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/git.c b/git.c index 39ba6b1

[PATCH V3 0/5] Git help option to list user guides

, as they overide any remaining arguments. The list of guides is spaced out in the same manner as the common command list. Philip Oakley (5): Show help: -a and -g option, and 'git help concept' usage. Help.c use OPT_BOOL and refactor logic Help.c add --guide option Help.c: add list_common_guides_help

Re: [PATCH V3 1/5] Show help: -a and -g option, and 'git help concept' usage.

Philip Oakley philipoak...@iee.org writes: Prepare for the addition of the -g --guides option to git help and show that help is available for both concept guides, and commands. Signed-off-by: Philip Oakley philipoak...@iee.org --- This should come at the end after you taught the -g option

Re: [PATCH] git help config: s/insn/instruction/

On 03/28/2013 06:59 AM, Junio C Hamano wrote: Matthias Krüger matthias.krue...@famsik.de writes: insn appears to be an in-code abbreviation and should not appear in manual/help pages. --- Thanks; sign-off? Oops, sorry. Signed-off-by: Matthias Krüger matthias.krue...@famsik.de (Is this

Re: [PATCH] git help config: s/insn/instruction/

Matthias Krüger matthias.krue...@famsik.de writes: On 03/28/2013 06:59 AM, Junio C Hamano wrote: Matthias Krüger matthias.krue...@famsik.de writes: insn appears to be an in-code abbreviation and should not appear in manual/help pages. --- Thanks; sign-off? Oops, sorry. Signed-off-by:

[PATCH] git help config: s/insn/instruction/

insn appears to be an in-code abbreviation and should not appear in manual/help pages. --- Documentation/config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/config.txt b/Documentation/config.txt index c1f435f..f79184c 100644 --- a/Documentation/config.txt

Re: [PATCH] git help config: s/insn/instruction/

Matthias Krüger matthias.krue...@famsik.de writes: insn appears to be an in-code abbreviation and should not appear in manual/help pages. --- Thanks; sign-off? -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo

[PATCH v2 0/5] Git help option to list user guides

This is the much truncated (was 0/13] and updated series for noting that 'git help' can display the existing guides that are formatted as man pages, and providing a 'git help' option to list a few of the most useful guides. The series is rebased on top of V1.8.2-rc1 Differences relative to V1

[PATCH v2 1/5] Show 'git help guide' usage, with examples

The git(1) man page must be accessed via 'git help git' on Git for Windows as it has no 'man' command. And it prompts users to read the git(1) page, rather than hoping they follow a subsidiary link within another documentation page. The 'tutorial' is an obvious guide to suggest. Signed-off

Re: [PATCH v2 1/5] Show 'git help guide' usage, with examples

Philip Oakley philipoak...@iee.org writes: The git(1) man page must be accessed via 'git help git' on Git for Windows as it has no 'man' command. And it prompts users to read the git(1) page, rather than hoping they follow a subsidiary link within another documentation page. The 'tutorial

[PATCH v2 0/5] [RESEND with Cc:] Git help option to list user guides

This is the much truncated (was 0/13] and updated series for noting that 'git help' can display the existing guides that are formatted as man pages, and providing a 'git help' option to list a few of the most useful guides. The series is rebased on top of V1.8.2-rc1 Differences relative to V1

  1   2   >