"brian m. carlson" <sandals@xxxxxxxxxxxxxxxxxxxx> 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/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html