From: Junio C Hamano <gitster@pobox.com>
To: Paul Tan <pyokagan@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2015, #01; Mon, 3)
Date: Mon, 03 Aug 2015 18:13:50 -0700 [thread overview]
Message-ID: <xmqqoain6ek1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACRoPnRj4apVat2oWVHvUgWdLp6RJZsWw-s=juB-Sdc3dL30ng@mail.gmail.com> (Paul Tan's message of "Tue, 4 Aug 2015 08:16:29 +0800")
Paul Tan <pyokagan@gmail.com> writes:
> I'm thinking about leaving them broken for now to push this patch
> series forward,...
Options upon restarting was not working at all with the old code
anyway, so that course of action sounds sensible.
Thanks.
prev parent reply other threads:[~2015-08-04 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 22:18 What's cooking in git.git (Aug 2015, #01; Mon, 3) Junio C Hamano
2015-08-03 22:41 ` Eric Sunshine
2015-08-04 1:12 ` Junio C Hamano
2015-08-04 0:16 ` Paul Tan
2015-08-04 1:13 ` Junio C Hamano [this message]
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=xmqqoain6ek1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pyokagan@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.