From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2016, #01; Tue, 2)
Date: Wed, 3 Aug 2016 14:24:57 +0200 [thread overview]
Message-ID: <d3fccd33-1aa2-7e91-9389-df6507861522@gmail.com> (raw)
In-Reply-To: <xmqqlh0ebyhn.fsf@gitster.mtv.corp.google.com>
W dniu 03.08.2016 o 00:24, Junio C Hamano pisze:
> --------------------------------------------------
> [Stalled]
>
> * jh/clean-smudge-annex (2016-08-01) 9 commits
> - use smudgeToFile filter in recursive merge
> - use smudgeToFile filter in git am
> - better recovery from failure of smudgeToFile filter
> - warn on unusable smudgeToFile/cleanFromFile config
> - use smudgeToFile in git checkout etc
> - use cleanFromFile in git add
> - add smudgeToFile and cleanFromFile filter configs
> - clarify %f documentation
> - Merge branch 'cc/apply-am' into HEAD
> (this branch uses cc/apply-am.)
>
> The interface to "clean/smudge" filters require Git to feed the
> whole contents via pipe, which is suboptimal for some applications.
> "cleanFromFile/smudgeToFile" commands are the moral equilvalents
> for these filters but they interact with the files on the
> filesystem directly.
>
> This is starting to bit-rot, as the topic it is built upon keeps
> getting rerolled. I _think_ I rebased it correctly, but I would
> not be surprised if I made a mistake.
>
> Will discard if/when I have to do another rebase, preferring to
> have a fresh reroll directly from the author.
Could you apply the first part (the first patch) of the series,
namely:
- clarify %f documentation
> * da/subtree-2.9-regression (2016-07-26) 2 commits
> (merged to 'next' on 2016-07-26 at 9d71562)
> + subtree: fix "git subtree split --rejoin"
> + t7900-subtree.sh: fix quoting and broken && chains
> (this branch is used by da/subtree-modernize.)
>
> "git merge" in Git v2.9 was taught to forbid merging an unrelated
> lines of history by default, but that is exactly the kind of thing
> the "--rejoin" mode of "git subtree" (in contrib/) wants to do.
> "git subtree" has been taught to use the "--allow-unrelated-histories"
> option to override the default.
>
> Will merge to 'master'.
Good. At least one Git user was bitten by this bug, see
<1BED74C8-2E4C-4CA7-B785-F0666B69C1A7@gmail.com>
P.S. I guess that filter.<driver>.process series is considered
pre-cooking?
--
Jakub Narębski
next prev parent reply other threads:[~2016-08-03 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 22:24 What's cooking in git.git (Aug 2016, #01; Tue, 2) Junio C Hamano
2016-08-03 12:24 ` Jakub Narębski [this message]
2016-08-03 15:29 ` Junio C Hamano
2016-08-04 8:03 ` Lars Schneider
2016-08-04 11:32 ` John Keeping
2016-08-04 14:00 ` Lars Schneider
2016-08-04 14:53 ` Johannes Schindelin
2016-08-04 16:02 ` 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
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=d3fccd33-1aa2-7e91-9389-df6507861522@gmail.com \
--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.
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).