From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #03; Wed, 24)
Date: Thu, 25 Nov 2010 08:26:50 -0800 (PST) [thread overview]
Message-ID: <m3ipzl4bfn.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vk4k2rt2m.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> * tr/config-doc (2010-10-24) 2 commits
> . Documentation: complete config list from other manpages
> . Documentation: Move variables from config.txt to separate file
>
> This unfortunately heavily conflicts with patches in flight...
The first patch in series can be automatically generated e.g. using
the following Perl script. I have succesfully rebased this series on
top of current 'master' using it (checkout + script + commit), see
't/doc-config-extraction' branch in my clone of git repo:
http://repo.or.cz/w/git/jnareb-git.git (can't push currently here)
http://github.com/jnareb/git
Though that doesn't help with issues with second patch in this series,
which were discussed on git mailing list when sending it.
-- >8 --
#!/usr/bin/perl
use strict;
use warnings;
my ($in, $out, $line);
open $in, '<', "Documentation/config.txt"
or die "$!";
open $out, '>', "Documentation/config.txt+"
or die "$!";
while ($line = <$in>) {
last if ($line =~ /^.*::$/);
print {$out} $line;
}
close $out;
open $out, '>', "Documentation/config-vars.txt"
or die "$!";
print {$out} $line;
while ($line = <$in>) {
print {$out} $line;
}
close $out;
open $out, '>>', "Documentation/config.txt+"
or die "$!";
print {$out} "include:config-vars.txt[]\n";
close $out;
rename "Documentation/config.txt+", "Documentation/config.txt"
or die "$!";
__END__
-- 8< --
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-11-25 16:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 3:16 What's cooking in git.git (Nov 2010, #03; Wed, 24) Junio C Hamano
2010-11-25 3:42 ` Jiang Xin
2010-11-25 9:45 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:35 ` Erik Faye-Lund
2010-11-25 12:00 ` Ævar Arnfjörð Bjarmason
2010-11-25 12:34 ` Erik Faye-Lund
2010-11-25 14:54 ` Erik Faye-Lund
2010-11-25 15:03 ` Erik Faye-Lund
2010-11-25 15:22 ` Erik Faye-Lund
2010-11-25 16:33 ` Ævar Arnfjörð Bjarmason
2010-11-25 17:55 ` Erik Faye-Lund
2010-11-25 18:06 ` Ævar Arnfjörð Bjarmason
2010-11-25 20:02 ` Erik Faye-Lund
2010-11-26 0:40 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:41 ` Johannes Sixt
2010-11-25 16:26 ` Jakub Narebski [this message]
2010-12-03 10:36 ` Thomas Rast
2010-12-03 11:13 ` Jakub Narebski
2010-12-03 11:22 ` Thomas Rast
2010-12-03 13:02 ` Jakub Narebski
2010-12-03 13:06 ` Thomas Rast
2010-12-03 14:12 ` Jakub Narebski
2010-12-03 15:03 ` Thomas Rast
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=m3ipzl4bfn.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.