From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 0/2] DEFAULT_DOC_TARGET
Date: Thu, 03 Jan 2013 14:20:31 -0800 [thread overview]
Message-ID: <7v4nixx61c.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130103210731.GB11783@sigill.intra.peff.net> (Jeff King's message of "Thu, 3 Jan 2013 16:07:31 -0500")
Jeff King <peff@peff.net> writes:
> Not surprising for such a large refactoring, but this has conflicts with
> what's in next. Here's the patch to apply on top of the conflicted tree
> you get from merging this with "next":
Yeah, verifying the manual fixup is a bit tricky indeed. The output from
$ git blame -C HEAD^.. -- config.mak.uname | grep '^[^^]'
shows only the first line of the resulting file, and the output from
$ git blame --reverse -C HEAD^.. -- Makefile | grep '^^'
shows only the three-line "Platform specific tweaks" comment, which
was replaced by your version in config.mak.uname, so nothing extra
was added and nothing important was lost between the two, it seems.
Thanks.
next prev parent reply other threads:[~2013-01-03 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 19:05 [PATCH v2 0/2] DEFAULT_DOC_TARGET Junio C Hamano
2013-01-03 19:05 ` [PATCH v2 1/2] Allow generating a non-default set of documentation Junio C Hamano
2013-01-03 19:05 ` [PATCH v2 2/2] Allow installing " Junio C Hamano
2013-01-03 20:32 ` [PATCH v2 0/2] DEFAULT_DOC_TARGET Jeff King
2013-01-03 20:37 ` Jeff King
2013-01-03 21:05 ` Jeff King
2013-01-03 21:07 ` Jeff King
2013-01-03 22:20 ` Junio C Hamano [this message]
2013-01-03 22:25 ` Jeff King
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=7v4nixx61c.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).