git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: David Glasser <glasser@davidglasser.net>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: push.default documented in "man git-push"?
Date: Wed, 3 Oct 2012 14:16:04 +0530	[thread overview]
Message-ID: <CALkWK0=N0OwTyu1KDAKzM48ioevGtmMNgy5gfK2J78zSPx7CVA@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8BB4WM1Lqz4yCGnGN2DV1Xsip3Qzh86ibBXwt2BnaNENA@mail.gmail.com>

[+CC: Junio, for comments]

Nguyen Thai Ngoc Duy wrote:
> On Wed, Oct 3, 2012 at 3:17 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
>> Hi Duy,
>>
>> Nguyen Thai Ngoc Duy wrote:
>>> Your patch is fine. I'm just thinking whether it's a good idea to add
>>> a section in the end of each command's man page to list all relevant
>>> config keys to that command, somewhat similar to "see also" section.
>>> It may help finding useful config keys that otherwise hard to find.
>>
>> That sounds like a good idea.  Would you like to write the first patch
>> (for git-push)?
>
> I won't be able to do it in the next 4 hours. If you want a stab at
> it, go ahead.

On second thought, it might not be such a good idea.  There are *lots*
of variables that control the operation of each command, and it's hard
to decide which ones to list and which ones to omit.  I've listed all
the relevant variables for git-push, except the advice.* variables- I
don't know how useful such a long list might be.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>

-- 8< --
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index cb97cc1..0a1c8d2 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -426,6 +426,30 @@ Commits A and B would no longer belong to a
branch with a symbolic name,
 and so would be unreachable.  As such, these commits would be removed by
 a `git gc` command on the origin repository.

+Configuration variables
+-----------------------
+
+These configuration variables affect the operation of git-push in
+various ways.  For more information see linkgit:git-config[1].
+
+branch.<name>.remote
+core.gitProxy
+http.proxy
+push.default
+receive.autogc
+receive.denyCurrentBranch
+receive.denyDeleteCurrent
+receive.denyDeletes
+receive.denyNonFastForwards
+receive.unpackLimit
+receive.updateserverinfo
+remote.<name>.mirror
+remote.<name>.proxy
+remote.<name>.push
+remote.<name>.pushurl
+remote.<name>.receivepack
+remote.<name>.url
+
 GIT
 ---
 Part of the linkgit:git[1] suite

  reply	other threads:[~2012-10-03  8:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02  0:25 push.default documented in "man git-push"? David Glasser
2012-10-02 15:09 ` Ramkumar Ramachandra
2012-10-02 15:18   ` David Glasser
2012-10-02 15:38     ` Ramkumar Ramachandra
2012-10-02 16:45       ` Matthieu Moy
2012-10-02 16:56         ` Ramkumar Ramachandra
2012-10-02 17:21         ` Junio C Hamano
2012-10-02 17:25           ` Matthieu Moy
2012-10-02 18:34       ` Junio C Hamano
2012-10-02 19:00         ` David Glasser
2012-10-02 19:08           ` Junio C Hamano
2012-10-03  7:54         ` Matthieu Moy
2012-10-03  8:52         ` Ramkumar Ramachandra
2012-10-03  8:14   ` Nguyen Thai Ngoc Duy
2012-10-03  8:17     ` Ramkumar Ramachandra
2012-10-03  8:23       ` Nguyen Thai Ngoc Duy
2012-10-03  8:46         ` Ramkumar Ramachandra [this message]
2012-10-03 10:18           ` Nguyen Thai Ngoc Duy
2012-10-03 18:26             ` Junio C Hamano
2012-10-03 21:40               ` Jeff King
2012-10-08 17:12                 ` Junio C Hamano
2012-10-07 16:09               ` Ramkumar Ramachandra
2012-10-07 20:27                 ` Junio C Hamano
2012-10-08  7:27                   ` Ramkumar Ramachandra
2012-10-08  8:35                     ` Nguyen Thai Ngoc Duy
2012-10-03 18:49             ` Junio C Hamano
2012-10-04  2:01               ` Nguyen Thai Ngoc Duy
2012-10-04  5:45                 ` Junio C Hamano
2012-10-05  6:34                   ` Nguyen Thai Ngoc Duy
2012-10-05 20:03                     ` Junio C Hamano
2012-10-11 12:43                       ` Nguyen Thai Ngoc Duy
2012-10-11 14:18                         ` Matthieu Moy
2012-10-11 14:43                           ` Nguyen Thai Ngoc Duy
2012-10-11 16:17                           ` Junio C Hamano
2012-10-03 11:58     ` Peter Krefting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALkWK0=N0OwTyu1KDAKzM48ioevGtmMNgy5gfK2J78zSPx7CVA@mail.gmail.com' \
    --to=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=glasser@davidglasser.net \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).