From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Ackermann <th.acker66@arcor.de>, git@vger.kernel.org
Subject: Re: [Patch 1/1] Wire html for all files in ./technical and ./howto in Makefile
Date: Mon, 12 Nov 2012 14:19:53 -0500 [thread overview]
Message-ID: <20121112191953.GA4623@sigill.intra.peff.net> (raw)
In-Reply-To: <7vpq3iiukk.fsf@alter.siamese.dyndns.org>
On Mon, Nov 12, 2012 at 09:45:31AM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > On Mon, Oct 29, 2012 at 07:33:47PM +0100, Thomas Ackermann wrote:
> >
> >> This patch addresses Junios comment in WC:
> >> "Misapplication of a patch fixed; the ones near the tip needs to
> >> update the links to point at the html files, though."
> >>
> >> See older mail in this thread:
> >> [...]
> >> That means that for the patch [6/8], which adds content-type to the
> >> text files, to be complete, it needs to update Makefile to produce
> >> html files from them.
> >> [...]
> >> So IMHO no open issues with this patch.
> >
> > OK, that explains the situation. Thanks, I'll merge it to master in the
> > next iteration.
>
> What happened to this topic?
I mistyped in the above response; it should have been "next" not
"master".
But then I forgot to merge it to next in the last iteration; it is
ta/doc-cleanup in pu, and is marked in "What's Cooking" to be merged to
next.
-Peff
next prev parent reply other threads:[~2012-11-12 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 17:55 [Patch 0/1] Makefile extensions for topic ta/doc-cleanup in pu Thomas Ackermann
2012-10-23 17:58 ` [Patch 1/1] Wire html for all files in ./technical and ./howto in Makefile Thomas Ackermann
2012-10-25 9:42 ` Jeff King
2012-10-29 18:33 ` Aw: " Thomas Ackermann
2012-10-29 21:57 ` Jeff King
2012-11-12 17:45 ` Junio C Hamano
2012-11-12 19:19 ` Jeff King [this message]
2012-11-12 20:13 ` Junio C Hamano
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=20121112191953.GA4623@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=th.acker66@arcor.de \
/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).