From: Junio C Hamano <firstname.lastname@example.org> To: Dan Jacques <email@example.com> Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: Question regarding "next" merge Date: Wed, 29 Nov 2017 11:18:59 +0900 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Dan Jacques's message of "Tue, 28 Nov 2017 20:38:48 -0500") Dan Jacques <email@example.com> writes: > I read the "what's cooking in Git" notes and saw that you were intending to > introduce this patch set into "next". Johannes pointed out some quoting errors > that break Windows builds, and I have incorporated fixes in my working copy. > > I was going to hold off on publishing v4 in case some of the other reviewers > had additional comments, but if you would prefer, I can publish them now > before you merge, so "next" doesn't break on Windows. Please do so. Even though I try to, I cannot follow and remember all discussions on each and every topic, and noticing your own topic getting mislabeled in "What's cooking" summary and yelling loudly at me is the best way to help the project overall by preventing me from mistakenly merging a topic that needs still an update. And if you are *not* ready and need a bit more time to send in an update, I'd prefer that you do *not* rush. I can easily make a note to wait for an update without merging the latest round of the topic I have in my tree. Also, I'll go offline towards the end of this week, so even if you rushed, the updated one may not hit my tree anyway. Thanks for stopping me.
next prev parent reply other threads:[~2017-11-29 2:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-27 16:40 [PATCH v3 0/4] RUNTIME_PREFIX relocatable Git Dan Jacques 2017-11-27 16:40 ` [PATCH v3 1/4] Makefile: generate Perl header from template file Dan Jacques 2017-11-27 16:40 ` [PATCH v3 2/4] Makefile: add support for "perllibdir" Dan Jacques 2017-11-27 16:40 ` [PATCH v3 3/4] Makefile: add Perl runtime prefix support Dan Jacques 2017-11-27 16:40 ` [PATCH v3 4/4] exec_cmd: RUNTIME_PREFIX on some POSIX systems Dan Jacques 2017-11-27 23:42 ` Johannes Schindelin 2017-11-28 3:25 ` Dan Jacques 2017-11-28 3:47 ` Junio C Hamano 2017-11-28 11:36 ` Johannes Schindelin 2017-11-29 1:38 ` Question regarding "next" merge Dan Jacques 2017-11-29 2:18 ` Junio C Hamano [this message] 2017-11-28 14:08 ` [PATCH v3 4/4] exec_cmd: RUNTIME_PREFIX on some POSIX systems Johannes Schindelin
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Question regarding "next" merge' \ /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
Code repositories for project(s) associated with this 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).