From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2009, #06; Wed, 25)
Date: Thu, 26 Nov 2009 02:15:58 +0100 [thread overview]
Message-ID: <fabb9a1e0911251715u661ce0aem79a4d700d552e105@mail.gmail.com> (raw)
In-Reply-To: <7v8wduksgq.fsf@alter.siamese.dyndns.org>
Heya,
On Thu, Nov 26, 2009 at 02:03, Junio C Hamano <gitster@pobox.com> wrote:
> * sr/vcs-helper (2009-11-18) 12 commits
> - Add Python support library for remote helpers
> - Basic build infrastructure for Python scripts
> - Allow helpers to report in "list" command that the ref is unchanged
> - Fix various memory leaks in transport-helper.c
> - Allow helper to map private ref names into normal names
> - Add support for "import" helper command
> - Allow specifying the remote helper in the url
> - Add a config option for remotes to specify a foreign vcs
> - Allow fetch to modify refs
> - Use a function to determine whether a remote is valid
> - Allow programs to not depend on remotes having urls
> - Fix memory leak in helper method for disconnect
>
> Replaced again, and looking good. Perhaps Daniel has some comments?
Indeed, Johan, Daniel, is the current version good for next?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-11-26 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 1:03 What's cooking in git.git (Nov 2009, #06; Wed, 25) Junio C Hamano
2009-11-26 1:15 ` Sverre Rabbelier [this message]
2009-11-26 7:37 ` Johan Herland
2009-11-27 19:17 ` Daniel Barkalow
2009-11-28 0:45 ` Sverre Rabbelier
2009-11-27 6:59 ` Jeff King
2009-11-27 14:45 ` Jonathan Nieder
2009-11-27 14:38 ` Breaking expectations in 1.7.0, was " Johannes Schindelin
2009-11-27 15:33 ` Jonathan Nieder
2009-11-27 18:32 ` Jonathan Nieder
2009-11-27 18:29 ` Junio C Hamano
2009-11-27 18:58 ` Jonathan Nieder
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=fabb9a1e0911251715u661ce0aem79a4d700d552e105@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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).