Hi, how to deal with patches during the v2.8.0 rc freeze? Will they wait on the mailing list until the feature release cycle is finished? Or if it's me who should act on this series, because it got below the radar during the rc freeze? To my knowledge there's only minor points that have to be discussed: On 02/29/2016 09:30 AM, Moritz Neeb wrote: > > Moritz Neeb (7): > quote: remove leading space in sq_dequote_step -- as in v2 in patch 1/7: How many spaces should be removed, cf.: http://thread.gmane.org/gmane.comp.version-control.git/285118/focus=287911 > bisect: read bisect paths with strbuf_getline() -- refined commit message > clean: read user input with strbuf_getline() -- simplified commit message > notes copy --stdin: read lines with strbuf_getline() -- switched with below > notes copy --stdin: split lines with string_list_split() -- switched with above in patches 4/7 and 5/7: Which commit should remove the trimming of "split[0]", cf.: http://thread.gmane.org/gmane.comp.version-control.git/285118/focus=287894 > remote: read $GIT_DIR/branches/* with strbuf_getline() -- as in v3 > wt-status: read rebase todolist with strbuf_getline() -- as in v2 > > bisect.c | 5 ++--- > builtin/clean.c | 6 +++--- > builtin/notes.c | 22 ++++++++++------------ > quote.c | 2 ++ > remote.c | 2 +- > wt-status.c | 3 +-- > 6 files changed, 19 insertions(+), 21 deletions(-) > -- 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