git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Stefan Beller <sbeller@google.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
	git-for-windows@googlegroups.com,
	Git Mailing List <git@vger.kernel.org>
Subject: Windows patches roadmap, was Re: On a personal note
Date: Fri, 18 Sep 2015 12:32:18 +0200	[thread overview]
Message-ID: <eff1c874e630dc60fdf3847efea95ff0@dscho.org> (raw)
In-Reply-To: <CAGZ79kaL6Rmmm6siN1nY-OnqK4ij_oboGgeNHz2dqYC6BKb6jQ@mail.gmail.com>

Hi Stefan,

[sorry that your mail to the git-for-windows Google Group got rejected; I want to try to keep this list subscribers-only as long as possible so as not to waste precious time on moderating 20+ spam mails per day, as we used to do with msysgit's mailing list.]

On 2015-09-17 21:27, Stefan Beller wrote:
> On Thu, Sep 17, 2015 at 11:54 AM, Johannes Schindelin
> <johannes.schindelin@gmx.de> wrote:
>>
>> And yes, the roadmap is pretty clear from the GitHub tickets, e.g. this one:
>>
>> https://github.com/git-for-windows/git/issues/285
> 
> That's pretty awesome. Glad it's on the roadmap!
> 
>>
>> Please note that I held off this week for three reasons:
>>
>> 1) I was submitting patches to the MSys2 and Cygwin upstream first,
>>
>> 2) I was busy fixing e.g. that bug where home directories containing non-ASCII characters were handled incorrectly (and generally trying to keep the tickets in https://github.com/git-for-windows/git under something similar to control), and
>>
>> 3) what with Peff's and Stefan's huge patch series, I did not want to overload Junio.
> 
> My patch series is not large by any means, but it seems as if it requires
> lots of discussion in the fine details. ;)

Yes, I actually meant the impact on the bandwidth of the Git mailing list, not the size of the patch series per se, sorry. I think that it is highly valuable what you are doing there, and I wish I had more time to participate in improving it... (but just when I think I have time, another bug report comes in, or some day-job stuff, or Junio releases a new version and I scramble to get a new Git for Windows version out... ;-))

Ciao,
Dscho

      reply	other threads:[~2015-09-18 10:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 10:00 On a personal note Johannes Schindelin
2015-09-04 12:43 ` Steve Hoelzer
2015-09-04 13:08 ` Jeff King
2015-09-04 16:10   ` Junio C Hamano
     [not found] ` <CACwWb3B-8iNhXXWo0N5whDy8pwUCyr5fA2SZuxP=tYd3jWB0SQ@mail.gmail.com>
2015-09-06 16:45   ` Johannes Schindelin
2015-09-17 13:29 ` Duy Nguyen
2015-09-17 18:54   ` Johannes Schindelin
2015-09-17 19:27     ` Stefan Beller
2015-09-18 10:32       ` Johannes Schindelin [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

  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=eff1c874e630dc60fdf3847efea95ff0@dscho.org \
    --to=johannes.schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=sbeller@google.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).