From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: RE: What's cooking in git.git (May 2014, #01; Tue, 6)
Date: Tue, 06 May 2014 18:17:30 -0500 [thread overview]
Message-ID: <53696d8aa12d2_747f15213089@nysa.notmuch> (raw)
In-Reply-To: <xmqqlhuecz1b.fsf@gitster.dls.corp.google.com>
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
next prev parent reply other threads:[~2014-05-06 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:39 What's cooking in git.git (May 2014, #01; Tue, 6) Junio C Hamano
2014-05-06 23:17 ` Felipe Contreras [this message]
2014-05-06 23:48 ` Junio C Hamano
2014-05-06 23:50 ` Felipe Contreras
2014-05-07 18:59 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53696d8aa12d2_747f15213089@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).