git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>,
	Derrick Stolee <stolee@gmail.com>,
	Olga Telezhnaya <olyatelezhnaya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2018, #01; Wed, 11)
Date: Wed, 11 Jul 2018 14:28:37 -0700	[thread overview]
Message-ID: <xmqqpnzt1myi.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqq7em138a5.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 11 Jul 2018 12:02:42 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> * jt/commit-graph-per-object-store (2018-07-09) 6 commits
> ...
>  Expecting a reroll, as it breaks 32-bit build.
>  cf. https://travis-ci.org/git/git/jobs/402422108

> * ot/ref-filter-object-info (2018-07-09) 4 commits
> ...
>  Expecting a reroll, as it breaks compilation with uninitialized var.
>  cf. https://travis-ci.org/git/git/jobs/402422102

> * ds/multi-pack-index (2018-07-09) 24 commits
> ...
>  Expecting a reroll to fix documentation build.
>  cf. https://travis-ci.org/git/git/jobs/402422110

I've added SQUASH??? patch at the tip of each of the above,
rebuilt 'pu' with them and pushed the result out.  It seems that
Travis is happier with the result.

Please do not forget to squash them in when/if rerolling.  If there
is no need to change anything else other than squashing them, you
can tell me to which commit in your series the fix needs to be
squashed in (that would save me time to figure it out, obviously).


  reply	other threads:[~2018-07-11 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 19:02 What's cooking in git.git (Jul 2018, #01; Wed, 11) Junio C Hamano
2018-07-11 21:28 ` Junio C Hamano [this message]
2018-07-13 19:52 ` Jeff King

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 \
    --in-reply-to=xmqqpnzt1myi.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.com \
    --cc=olyatelezhnaya@gmail.com \
    --cc=stolee@gmail.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. 
Code repositories for project(s) associated with this public 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).