git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Thomas Rast <trast@student.ethz.ch>
Subject: [PATCHv4 0/2] Documentation: refactor config variable descriptions
Date: Tue, 21 Jun 2011 22:36:57 +0200	[thread overview]
Message-ID: <20110621203041.11131.90701.stgit@localhost.localdomain> (raw)

This is something that I noticed while doing cleanup of old unused
branches.

Last version of this series was sent (IIRC) on 22.10.2010 as

  [RFC PATCH v2 0/3] Documentation: refactor config variable descriptions
  http://thread.gmane.org/gmane.comp.version-control.git/159641

This series is without

      Documentation: move format.* documentation to format-patch

Rebasing it on top of current version was easy, even though there were
many conflicts. I simply used the script in commit message of first
patch to extract config-vars.txt file automatically.
---
Thomas Rast (2):
      Documentation: complete config list from other manpages
      Documentation: Move variables from config.txt to separate file

 Documentation/Makefile              |   10 
 Documentation/config-vars-src.txt   | 1760 +++++++++++++++++++++++++++++++++++
 Documentation/config.txt            | 1759 -----------------------------------
 Documentation/make-config-list.perl |  234 +++++
 4 files changed, 2005 insertions(+), 1758 deletions(-)
 create mode 100644 Documentation/config-vars-src.txt
 create mode 100755 Documentation/make-config-list.perl

-- 
Jakub Narebski
ShadeHawk on #git
Poland

                 reply	other threads:[~2011-06-21 20:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=20110621203041.11131.90701.stgit@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=trast@student.ethz.ch \
    /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.
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 NNTP newsgroup(s).