From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2015, #07; Mon, 27)
Date: Fri, 31 Jul 2015 21:37:17 +0000 [thread overview]
Message-ID: <20150731213716.GA488564@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <vpqoaiu9dci.fsf@anie.imag.fr>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Thu, Jul 30, 2015 at 11:58:05AM +0200, Matthieu Moy wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > On Mon, Jul 27, 2015 at 02:23:04PM -0700, Junio C Hamano wrote:
> >> * bc/object-id (2015-06-17) 10 commits
> > Is there anything I can do to make this series less painful (e.g. a
> > reroll or such)?
>
> For the GSoC part, "Suggested 'pencils down' date" is August 17th. The
> "Firm 'pencils down date'" is on 21th, so things should stabilize.
>
> On the "unify ref-listing commands" side, the big code movement is in
> kn/for-each-ref which should hit master soon, but there are other less
> intrusive series active.
>
> (That doesn't really answer your question, but may be relevant
> information)
It's certainly helpful to know the timeline. I'm fine with waiting, but
I anticipate that there will be pain when it finally goes into pu, and
if there's anything I can do to minimize that, I'd like to.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2015-07-31 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 21:23 What's cooking in git.git (Jul 2015, #07; Mon, 27) Junio C Hamano
2015-07-30 0:29 ` brian m. carlson
2015-07-30 9:58 ` Matthieu Moy
2015-07-31 21:37 ` brian m. carlson [this message]
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=20150731213716.GA488564@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.