Re: What's cooking in git.git (May 2014, #01; Tue, 6)

2014-05-07 Thread Junio C Hamano 
Felipe Contreras felipe.contre...@gmail.com writes:

 Junio C Hamano wrote:
 Felipe Contreras felipe.contre...@gmail.com writes:
  Plus this one which has been completely ignored:
 
 completion: move out of contrib
 
 It is not about ignored.  It is about running out of time before
 concluding the day's integration.

 A comment doesn't require integration.

It requires time and attention that are limited commodities.
Moreover, I won't read or respond to pieces of e-mail in the order
they come in.

The topics listed in the What's cooking report is fixed at the end
of the day's integration cycle, as they are essentially output of
log --first-parent master..pu | grep Merge.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: What's cooking in git.git (May 2014, #01; Tue, 6)

2014-05-06 Thread Felipe Contreras 
Junio C Hamano wrote:
 * fc/remote-helpers-hg-bzr-graduation (2014-04-29) 11 commits
  - remote-hg: trivial cleanups
  - remote-hg: make sure we omit multiple heads
  - git-remote-hg: use internal clone's hgrc
  - t: remote-hg: split into setup test
  - remote-hg: properly detect missing contexts
  - remote-{hg,bzr}: store marks only on success
  - remote-hg: update to 'public' phase when pushing
  - remote-hg: fix parsing of custom committer
   (merged to 'next' on 2014-04-22 at fed170a)
  + remote-helpers: move tests out of contrib
  + remote-helpers: move out of contrib
  + remote-helpers: squelch python import exceptions
 
  Move remote-hg and remote-bzr out of contrib/.  There were some
  suggestions on the follow-up fix patches still not in 'next', which
  may result in a reroll.

I've no idea what suggestions you are talking about.

  I tend to agree with John Keeping that remote helpers that are
  actively maintained can and should aim to graduate from my tree and
  given to the user directly.

Wait, I was under the impression the graduation was going to happen for
v2.0.

I don't understand what is the point of preparing the v2.0 for so long,
and then all of a sudden tag v2.0.0-rc0 and say oops! if you wanted to
get something into v2.0 it's too late now, wait another 2-10 years for
important changes to get merged.

Such a wasted opportunity and such a disappointing release.

Therefore the release notes are still lying to the users:

 * git push via transport-helper interface (e.g. remote-hg) has
   been updated to allow ref deletion in a way similar to the natively
   supported transports.

That is not true.

These should obviously be part of the v2.0:

* fc/remote-helpers-hg-bzr-graduation (2014-04-29) 11 commits
 + remote-helpers: move tests out of contrib
 + remote-helpers: move out of contrib
 + remote-helpers: squelch python import exceptions
 - remote-{hg,bzr}: store marks only on success

* fc/remote-helper-refmap (2014-04-21) 8 commits
  (merged to 'next' on 2014-04-22 at fb5a4c2)
 + transport-helper: remove unnecessary strbuf resets
 + transport-helper: add support to delete branches
 + fast-export: add support to delete refs
 + fast-import: add support to delete refs
 + transport-helper: add support to push symbolic refs
 + transport-helper: add support for old:new refspec
 + fast-export: add new --refspec option
 + fast-export: improve argument parsing

* fc/merge-default-to-upstream (2014-04-22) 1 commit
 + merge: enable defaulttoupstream by default

* fc/mergetool-prompt (2014-04-24) 2 commits
 + mergetool: document the default for --[no-]prompt
 + mergetool: run prompt only if guessed tool

Plus this one which has been completely ignored:

   completion: move out of contrib


Since you are not going to do so, I do not feel compelled to fix the
synchronization crash regression that is present in v2.0.0-rc2 and I
already warned you about.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: What's cooking in git.git (May 2014, #01; Tue, 6)

2014-05-06 Thread Junio C Hamano 
Felipe Contreras felipe.contre...@gmail.com writes:

 Therefore the release notes are still lying to the users:

  * git push via transport-helper interface (e.g. remote-hg) has
been updated to allow ref deletion in a way similar to the natively
supported transports.

 That is not true.

Hmph, you are right.  I somehow mislabeled the series that ends at
a7cb1276cc263446b19b43d3a7784cbc72f84e28 dealing with delete, when
the series actually is about forcing.  Will update.

 Plus this one which has been completely ignored:

completion: move out of contrib

It is not about ignored.  It is about running out of time before
concluding the day's integration.

I can hopefully queue it on 'pu' tomorrow, and depending on the
reviews or lack of reviews, it may advance on its own pace from
there.

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: What's cooking in git.git (May 2014, #01; Tue, 6)

2014-05-06 Thread Felipe Contreras 
Junio C Hamano wrote:
 Felipe Contreras felipe.contre...@gmail.com writes:
  Plus this one which has been completely ignored:
 
 completion: move out of contrib
 
 It is not about ignored.  It is about running out of time before
 concluding the day's integration.

A comment doesn't require integration.

Either way the rest of the patches have already advanced.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html