Junio C Hamano wrote: > Two announcements for their version 0.2 on the list archive are not > quite enough to advertise them to their users. > > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- > > * I am inclined to queue this for 2.0, and we would also need an > update to the release notes as well. > > I am undecided about the revert I sent earlier in $gmane/248937; > with or without it, that is just a contrib/ thing that is not > well maintained inside our tree anyway. > > contrib/remote-helpers/README | 11 +++++++++++ > 1 file changed, 11 insertions(+) > create mode 100644 contrib/remote-helpers/README NAK. > diff --git a/contrib/remote-helpers/README b/contrib/remote-helpers/README > new file mode 100644 > index 0000000..72a2df4 > --- /dev/null > +++ b/contrib/remote-helpers/README > @@ -0,0 +1,11 @@ > +The remote-helper bridges to access data stored in Hg and bzr will be They are called Mercurial and Bazaar. > +maintained outside the git.git tree in the repositories of its > +primary author at: > + > + https://github.com/felipec/git-remote-hg > + https://github.com/felipec/git-remote-bzr If this is formatted in asciidoc the links won't appear as links. Do it as I did: * https://github.com/felipec/git-remote-hg * https://github.com/felipec/git-remote-bzr > +As a convenience, copies of the last-bundled version of these two > +remote-helper bridges are kept here, but they may left stale. Users > +are encouraged to visit the above authoritative repositories for the > +latest versions to get involved in its further developments. 1) Most users will *never* see this README 2) Most packagers will never see this README 3) The people that do read this README will wonder *why* they are now maintained separately. Thanks for wasting all my hard work and sabotaging these projects. Just as a heads-up. I *will* complain about this publicly and my blog is visited by thousands of people. I am requesting one last time: 1) Add warnings *directly* into the tools themselves ASAP You didn't have any problems adding warnings for pre-v2.0 behavior that changed, nor did you have a problem adding the warning about the new zsh completion that moved out of the bash one. Why would you have a problem with this one? 2) Replace the tools with stubs that point to the right locations at the earliest convenience I already sent patches for both, and they were ignored. A failure to do both will result in a lack of visibility of the new projects, and a decrease in the quality the users of git.git contrib area's remote-helpers receive. I will consider that a deliberate attempt to make the new projects experience unnecessary hardship. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html