Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:55:18

Torsten Bögershausen [off-list ref] writes:
My understanding:
Either use people cygwin 1.5 or they use cygwin 1.7, and in this case
the installation is updated frequently.

Peff or Junio, please go ahead with the patch.

If it turns out that we want to support cygwin installations like 1.7.7
which could be upgraded, but are not upgraded since they are
"production machines we do not dare to touch" we can still improve
the autodetection.
OK.  I moved the topic forward but we may still want to rename the
name of the macro to have CYGWIN somewhere in the name.

Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)

From: Torsten Bögershausen <hidden>
Date: 2016-06-15 22:55:18

On 16.11.12 19:52, Junio C Hamano wrote:
Torsten Bögershausen [off-list ref] writes:
quoted
My understanding:
Either use people cygwin 1.5 or they use cygwin 1.7, and in this case
the installation is updated frequently.

Peff or Junio, please go ahead with the patch.

If it turns out that we want to support cygwin installations like 1.7.7
which could be upgraded, but are not upgraded since they are
"production machines we do not dare to touch" we can still improve
the autodetection.
OK.  I moved the topic forward but we may still want to rename the
name of the macro to have CYGWIN somewhere in the name.
I send a patch some seconds ago.
I forgot to mention that this should be applied to next
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help