Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Nov 2016, #04; Mon, 21)
Date: Mon, 21 Nov 2016 15:14:25 -0800	[thread overview]
Message-ID: <xmqqh970h1da.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kbCebHojPDUdHn2mmjUwRe-FOcnJqtoa828PJwC6P5mNw@mail.gmail.com> (Stefan Beller's message of "Mon, 21 Nov 2016 14:57:43 -0800")

Stefan Beller <sbeller@google.com> writes:

>> * bw/grep-recurse-submodules (2016-11-18) 6 commits
>>  - grep: search history of moved submodules
>>  - grep: enable recurse-submodules to work on <tree> objects
>>  - grep: optionally recurse into submodules
>>  - grep: add submodules as a grep source type
>>  - submodules: load gitmodules file from commit sha1
>>  - submodules: add helper functions to determine presence of submodules
>>
>>  "git grep" learns to optionally recurse into submodules
>>
>>  Waiting for review.
>
> I did review both off and on list and I think the latest version is good.

I thought that there were strange mixups of two enumeration types
that are incompatible, at least.  Is there an update that I didn't
see, or you didn't read problems pointed out on list?

>> * jt/use-trailer-api-in-commands (2016-11-02) 6 commits
>>  - sequencer: use trailer's trailer layout
>>  - trailer: have function to describe trailer layout
>>  - trailer: avoid unnecessary splitting on lines
>>  - commit: make ignore_non_trailer take buf/len
>>  - SQUASH???
>>  - trailer: be stricter in parsing separators
>>
>>  Commands that operate on a log message and add lines to the trailer
>>  blocks, such as "format-patch -s", "cherry-pick (-x|-s)", and
>>  "commit -s", have been taught to use the logic of and share the
>>  code with "git interpret-trailer".
>>
>>  What's the doneness of this topic?
>
> From a cursory read (with the SQUASH applied)
> this seems to be done to me.

We are not all that in a hurry to move non-fix to 'next' only with a
cursory read at this point in the cycle ;-).

>> * sb/submodule-config-cleanup (2016-11-02) 3 commits
>> - submodule-config: clarify parsing of null_sha1 element
>> - submodule-config: rename commit_sha1 to commit_or_tree
>> - submodule config: inline config_from_{name, path}
>>
>>  What's the doneness of this topic?
>
> Jake Keller reviewed this and it turns out I was not careful in patch 2/3.
>
> Will resend.

OK.  Thanks.

  parent reply	other threads:[~2016-11-21 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 22:19 What's cooking in git.git (Nov 2016, #04; Mon, 21) Junio C Hamano
2016-11-21 22:57 ` Stefan Beller
2016-11-21 23:05   ` Junio C Hamano
2016-11-21 23:14   ` Junio C Hamano [this message]
2016-11-21 23:19     ` Stefan Beller

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=xmqqh970h1da.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sbeller@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox