git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: preview: What's cooking in git.git (Jun 2016, #10; Tue, 28)
Date: Wed, 29 Jun 2016 07:41:36 +0200	[thread overview]
Message-ID: <57735F90.1010907@kdbg.org> (raw)
In-Reply-To: <20160629014342.GA28661@sigill.intra.peff.net>

Am 29.06.2016 um 03:43 schrieb Jeff King:
> Another is to just put the posix/ksh schemes into the helper function,
> and let Windows people sort it out later if they want to.

Let's do this.

-- Hannes


  parent reply	other threads:[~2016-06-29  5:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 23:36 preview: What's cooking in git.git (Jun 2016, #10; Tue, 28) Junio C Hamano
2016-06-29  1:43 ` Jeff King
2016-06-29  2:39   ` Junio C Hamano
2016-06-29  5:41   ` Johannes Sixt [this message]
2016-06-30  8:16     ` Jeff King
2016-06-29 11:47 ` Johannes Schindelin
2016-06-29 16:57   ` Junio C Hamano
2016-07-02  7:32     ` Johannes Schindelin
2016-06-30  6:26   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57735F90.1010907@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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 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 NNTP newsgroup(s).