All of lore.kernel.org
 help / color / mirror / Atom feed
* Do you plan to release 2.5.2 any time soon?
@ 2015-09-02 22:40 Johannes Schindelin
  2015-09-03 19:00 ` Junio C Hamano
  0 siblings, 1 reply; 3+ messages in thread
From: Johannes Schindelin @ 2015-09-02 22:40 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git

Hi Junio,

I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do
you plan to release 2.5.2 any time soon? If yes, I would hold off,
otherwise I will just do a Git for Windows 2.5.1 (Rel 2).

Thanks,
Dscho

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Do you plan to release 2.5.2 any time soon?
  2015-09-02 22:40 Do you plan to release 2.5.2 any time soon? Johannes Schindelin
@ 2015-09-03 19:00 ` Junio C Hamano
  2015-09-04  7:08   ` Johannes Schindelin
  0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2015-09-03 19:00 UTC (permalink / raw)
  To: Johannes Schindelin; +Cc: git

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do
> you plan to release 2.5.2 any time soon? If yes, I would hold off,
> otherwise I will just do a Git for Windows 2.5.1 (Rel 2).

Among the topics marked for possible later merging to 'maint' in the
draft release notes to 2.6, candidates for future maintenance
snapshots are:

* mh/get-remote-group-fix # 4 (2 weeks ago) 
* cb/open-noatime-clear-errno # 1 (9 days ago) 
* jk/long-error-messages # 2 (9 days ago) 
* jh/strbuf-read-use-read-in-full # 1 (9 days ago) 
* ps/t1509-chroot-test-fixup # 2 (2 weeks ago) 
* sg/help-group # 1 (8 days ago) 
* nd/dwim-wildcards-as-pathspecs # 1 (9 days ago) 
* jk/fix-alias-pager-config-key-warnings # 1 (3 days ago) 
* jk/rev-list-has-no-notes # 1 (3 days ago) 
* nd/fixup-linked-gitdir # 1 (2 days ago) 
* as/docfix-reflog-expire-unreachable # 1 (8 days ago) 
* sg/t3020-typofix # 1 (8 days ago) 
* po/po-readme # 1 (8 days ago) 
* sg/wt-status-header-inclusion # 1 (8 days ago) 
* ss/fix-config-fd-leak # 1 (8 days ago) 
* jc/calloc-pathspec # 1 (8 days ago) 
* rs/archive-zip-many # 3 (2 days ago) 
* dt/commit-preserve-base-index-upon-opportunistic-cache-tree-update # 1 (2 days ago) 
* cc/trailers-corner-case-fix # 3 (22 hours ago) 
* jk/log-missing-default-HEAD # 1 (22 hours ago) 
* ee/clean-test-fixes # 1 (22 hours ago) 

These I deem are safe (not just the changes themselves are trivially
correct but it is unlikely to make things gravely worse if it turns
out there were ramifications no reviewers thought about with them)
and can go in 2.5.2.

As to other topics that are in 'master' but not in the above list, I
do not have doubt about their value (otherwise they would not be in
'master' in the first place), but either they are still too young in
'master' or are with sufficiently big impact on the callchain that
it is not entirely implausible that they have risks of unforeseen
ramifications and fallouts.

Let's aim to tag 2.5.2 soonish, before mid next-week at the latest.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Do you plan to release 2.5.2 any time soon?
  2015-09-03 19:00 ` Junio C Hamano
@ 2015-09-04  7:08   ` Johannes Schindelin
  0 siblings, 0 replies; 3+ messages in thread
From: Johannes Schindelin @ 2015-09-04  7:08 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git

Hi Junio,

On 2015-09-03 21:00, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
>> I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do
>> you plan to release 2.5.2 any time soon? If yes, I would hold off,
>> otherwise I will just do a Git for Windows 2.5.1 (Rel 2).
> 
> Among the topics marked for possible later merging to 'maint' in the
> draft release notes to 2.6, candidates for future maintenance
> snapshots are:
> 
> * mh/get-remote-group-fix # 4 (2 weeks ago) 
> * cb/open-noatime-clear-errno # 1 (9 days ago) 
> * jk/long-error-messages # 2 (9 days ago) 
> * jh/strbuf-read-use-read-in-full # 1 (9 days ago) 
> * ps/t1509-chroot-test-fixup # 2 (2 weeks ago) 
> * sg/help-group # 1 (8 days ago) 
> * nd/dwim-wildcards-as-pathspecs # 1 (9 days ago) 
> * jk/fix-alias-pager-config-key-warnings # 1 (3 days ago) 
> * jk/rev-list-has-no-notes # 1 (3 days ago) 
> * nd/fixup-linked-gitdir # 1 (2 days ago) 
> * as/docfix-reflog-expire-unreachable # 1 (8 days ago) 
> * sg/t3020-typofix # 1 (8 days ago) 
> * po/po-readme # 1 (8 days ago) 
> * sg/wt-status-header-inclusion # 1 (8 days ago) 
> * ss/fix-config-fd-leak # 1 (8 days ago) 
> * jc/calloc-pathspec # 1 (8 days ago) 
> * rs/archive-zip-many # 3 (2 days ago) 
> * dt/commit-preserve-base-index-upon-opportunistic-cache-tree-update #
> 1 (2 days ago)
> * cc/trailers-corner-case-fix # 3 (22 hours ago) 
> * jk/log-missing-default-HEAD # 1 (22 hours ago) 
> * ee/clean-test-fixes # 1 (22 hours ago) 
> 
> These I deem are safe (not just the changes themselves are trivially
> correct but it is unlikely to make things gravely worse if it turns
> out there were ramifications no reviewers thought about with them)
> and can go in 2.5.2.
> 
> As to other topics that are in 'master' but not in the above list, I
> do not have doubt about their value (otherwise they would not be in
> 'master' in the first place), but either they are still too young in
> 'master' or are with sufficiently big impact on the callchain that
> it is not entirely implausible that they have risks of unforeseen
> ramifications and fallouts.
> 
> Let's aim to tag 2.5.2 soonish, before mid next-week at the latest.

Okay!

Thank you,
Dscho

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-09-04  7:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-02 22:40 Do you plan to release 2.5.2 any time soon? Johannes Schindelin
2015-09-03 19:00 ` Junio C Hamano
2015-09-04  7:08   ` Johannes Schindelin

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.