git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
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: Thu, 30 Jul 2015 11:58:05 +0200	[thread overview]
Message-ID: <vpqoaiu9dci.fsf@anie.imag.fr> (raw)
In-Reply-To: <20150730002925.GF809807@vauxhall.crustytoothpaste.net> (brian m. carlson's message of "Thu, 30 Jul 2015 00:29:25 +0000")

"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
>>  . remote.c: use struct object_id in many functions
>>  . object-id: use struct object_id in struct object
>>  . remote.c: use struct object_id in ref_newer()
>>  . transport-helper.c: use struct object_id in push_refs_with_export()
>>  . connect.c: use struct object_id in get_remote_heads()
>>  . remote-curl: use struct object_id in parse_fetch()
>>  . fetch-pack: use struct object_id in add_sought_entry_mem()
>>  . object_id: convert struct ref to use object_id.
>>  . sha1_file: introduce has_object_file() helper
>>  . refs: convert some internal functions to use object_id
>> 
>>  More transition from "unsigned char[40]" to "struct object_id".
>> 
>>  While GSoC and other topics are actively moving existing code
>>  around, this cannot go in; ejected from 'pu'.
>
> 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)

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2015-07-30  9:58 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 [this message]
2015-07-31 21:37     ` brian m. carlson

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=vpqoaiu9dci.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sandals@crustytoothpaste.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).