Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-05 Thread Junio C Hamano
Mark Levedahl writes: > I have been using this patch since Ramsey first sent it, have noticed > no trouble over that time but all of my work is with filemode=true > (has been since I started using git as Cygwin is a secondary platform > for me and interoperability with repos on Linux is an absolu

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-03 Thread Mark Levedahl
On 08/01/2013 05:12 PM, Junio C Hamano wrote: Ramsay Jones writes: Junio C Hamano wrote: Ramsay Jones writes: I am personally in favor of this simpler solution. Comments? I had expected this to me marked for 'master'. Has this simply been overlooked, or do you have reservations about

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-03 Thread Torsten Bögershausen
On 2013-08-03 08.50, Torsten Bögershausen wrote: > On 2013-08-01 22.51, Ramsay Jones wrote: >> Junio C Hamano wrote: >>> Ramsay Jones writes: >>> > I am personally in favor of this simpler solution. Comments? I had expected this to me marked for 'master'. Has this simply

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-02 Thread Torsten Bögershausen
On 2013-08-01 22.51, Ramsay Jones wrote: > Junio C Hamano wrote: >> Ramsay Jones writes: >> I am personally in favor of this simpler solution. Comments? >>> >>> I had expected this to me marked for 'master'. >>> >>> Has this simply been overlooked, or do you have reservations about >>> appl

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-01 Thread Junio C Hamano
Ramsay Jones writes: > Junio C Hamano wrote: >> Ramsay Jones writes: >> I am personally in favor of this simpler solution. Comments? >>> >>> I had expected this to me marked for 'master'. >>> >>> Has this simply been overlooked, or do you have reservations about >>> applying this patch?

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-08-01 Thread Ramsay Jones
Junio C Hamano wrote: > Ramsay Jones writes: > >>> I am personally in favor of this simpler solution. Comments? >> >> I had expected this to me marked for 'master'. >> >> Has this simply been overlooked, or do you have reservations about >> applying this patch? > > I am just being careful and

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-07-31 Thread Junio C Hamano
Ramsay Jones writes: >> I am personally in favor of this simpler solution. Comments? > > I had expected this to me marked for 'master'. > > Has this simply been overlooked, or do you have reservations about > applying this patch? I am just being careful and do want to keep it cooking in 'next'

Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-07-31 Thread Ramsay Jones
Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. > > The shape of the upcoming release is pretty much known by now; all > the topics that are marked for 'master' in

What's cooking in git.git (Jul 2013, #09; Mon, 29)

2013-07-29 Thread Junio C Hamano
Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The shape of the upcoming release is pretty much known by now; all the topics that are marked for 'master' in this issue will likely to be in th