From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2016, #08; Tue, 27)
Date: Fri, 30 Sep 2016 18:33:44 -0700 [thread overview]
Message-ID: <CAGZ79kY6c-vwSP7-1Gz4jwWO-z_yT2oFbG4cgZb-JAae=Sk-cA@mail.gmail.com> (raw)
In-Reply-To: <xmqq8tudkjvn.fsf@gitster.mtv.corp.google.com>
>
>
> * jc/attr (2016-05-25) 18 commits
> - attr: support quoting pathname patterns in C style
> - attr: expose validity check for attribute names
> - attr: add counted string version of git_attr()
> - attr: add counted string version of git_check_attr()
> - attr: retire git_check_attrs() API
> - attr: convert git_check_attrs() callers to use the new API
> - attr: convert git_all_attrs() to use "struct git_attr_check"
> - attr: (re)introduce git_check_attr() and struct git_attr_check
> - attr: rename function and struct related to checking attributes
> - attr.c: plug small leak in parse_attr_line()
> - attr.c: tighten constness around "git_attr" structure
> - attr.c: simplify macroexpand_one()
> - attr.c: mark where #if DEBUG ends more clearly
> - attr.c: complete a sentence in a comment
> - attr.c: explain the lack of attr-name syntax check in parse_attr()
> - attr.c: update a stale comment on "struct match_attr"
> - attr.c: use strchrnul() to scan for one line
> - commit.c: use strchrnul() to scan for one line
> (this branch is used by jc/attr-more, sb/pathspec-label and sb/submodule-default-paths.)
>
> The attributes API has been updated so that it can later be
> optimized using the knowledge of which attributes are queried.
>
> I wanted to polish this topic further to make the attribute
> subsystem thread-ready, but because other topics depend on this
> topic and they do not (yet) need it to be thread-ready.
>
> As the authors of topics that depend on this seem not in a hurry,
> let's discard this and dependent topics and restart them some other
> day.
>
> Will discard.
So I just realized this is a big hint for me to pick up that topic; I assumed
you'd want to tackle the attr subsystem eventually, so all I was doing, was
waiting for your motivation to look at attr stuff to come back.
So what is the actual lacking stuff here?
Thanks,
Stefan
next prev parent reply other threads:[~2016-10-01 1:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 23:23 What's cooking in git.git (Sep 2016, #08; Tue, 27) Junio C Hamano
2016-10-01 1:33 ` Stefan Beller [this message]
2016-10-03 18:07 ` Junio C Hamano
2016-10-03 19:55 ` Stefan Beller
2016-10-03 20:17 ` Junio C Hamano
2016-10-03 20:49 ` Junio C Hamano
2016-10-03 21:49 ` Stefan Beller
2016-10-03 21:56 ` Junio C Hamano
2016-10-03 22:17 ` Stefan Beller
2016-10-04 16:11 ` Junio C Hamano
2016-10-04 22:36 ` 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
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='CAGZ79kY6c-vwSP7-1Gz4jwWO-z_yT2oFbG4cgZb-JAae=Sk-cA@mail.gmail.com' \
--to=sbeller@google.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).