git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 6, 2014, 23:17 UTC
Message-ID
<53696d8aa12d2_747f15213089@nysa.notmuch>
In-Reply-To
<xmqqlhuecz1b.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
Show 17 quoted lines
> * 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
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “What's cooking in git.git (May 2014, #01; Tue, 6)”
  1. Junio C HamanoMay 6, 2014
  2. Felipe ContrerasMay 6, 2014
  3. Junio C HamanoMay 6, 2014
  4. Felipe ContrerasMay 6, 2014
  5. Junio C HamanoMay 7, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.