All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: What's cooking in git.git (Sep 2012, #05; Fri, 14)
Date: Mon, 17 Sep 2012 09:19:50 +0200	[thread overview]
Message-ID: <003c01cd94a4$d4bc73c0$7e355b40$@schmitz-digital.de> (raw)
In-Reply-To: 

> From: Joachim Schmitz [mailto:jojo@schmitz-digital.de]
> Sent: Saturday, September 15, 2012 7:15 PM
> To: 'Junio C Hamano'
> Cc: 'git@vger.kernel.org'
> Subject: RE: What's cooking in git.git (Sep 2012, #05; Fri, 14)
> 
> > From: Junio C Hamano [mailto:gitster@pobox.com]
> > Sent: Saturday, September 15, 2012 7:01 PM
> > To: Joachim Schmitz
> > Cc: git@vger.kernel.org
> > Subject: Re: What's cooking in git.git (Sep 2012, #05; Fri, 14)
> >
> > "Joachim Schmitz" <jojo@schmitz-digital.de> writes:
> >
> > > Junio C Hamano wrote:
> > >> I think we can start thinking about feature freeze once the topics
> > >> in 'next' that are scheduled to graduate to 'master' already are
> > >> fully cooked.  For any late-coming topic, there always is the next
> > >> cycle ;-)
> > >
> > > I've not hear anything about my poll patches and I'd really like them
> > > to into 1.8.x.
> >
> > I've seen some patches on "poll" posted, were discussed and had
> > threads titled "Re: [PATCH] ...".  But I didn't see a rerolled
> > "[PATCH v2 n/m] ..." series that states that it is a rerolled
> > "hopefully final version" that addresses all the points that were
> > brought up during the discussion that need to be addressed.
> >
> > I do not necessarily follow all the minute details of all discussion
> > threads.  For this particular series, I not know which ones of your
> > "poll patches" turned out to be unneeded, which ones turned out to
> > be fine as posted originally and which ones needed updating.
> 
> There were several iterations up to [PATCH v4 n/4] and only one foreign comment to it (and to some commented code) and one self-
> comment about the order of patches, but none about technical correctness, none that I remember at least.
> 
> I can post a v5 series which will

Actually v6, seems I got myself confused in what I send already, one part of the series was on v5 already, aother on v4 and yet
another still on v3.

> - move compat/win32/poll.[ch] to compat/poll/ and adjust Makefile
> - #ifdef some WIN32 specific #include (should this be done in one step with the above?)

Decided for 2 patches

> - fix the 2 bugs in poll.c just like they got fixed in gnulib's version (would you want this in one or two steps?)

Likewise
 
Bye, Jojo

      parent reply	other threads:[~2012-09-17  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 21:24 What's cooking in git.git (Sep 2012, #05; Fri, 14) Junio C Hamano
2012-09-15 10:08 ` Joachim Schmitz
2012-09-15 17:01   ` Junio C Hamano
2012-09-15 17:15     ` Joachim Schmitz
2012-09-17  7:19     ` Joachim Schmitz [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='003c01cd94a4$d4bc73c0$7e355b40$@schmitz-digital.de' \
    --to=jojo@schmitz-digital.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.