From: "Andrzej K. Haczewski" <ahaczewski@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>,
Johan Herland <johan@herland.net>
Subject: Re: [PATCH v3 11/12] Basic build infrastructure for Python scripts
Date: Sat, 7 Nov 2009 00:23:06 +0100 [thread overview]
Message-ID: <16cee31f0911061523v5b9754ebg9c846c0e96ac808@mail.gmail.com> (raw)
In-Reply-To: <1257547966-14603-12-git-send-email-srabbelier@gmail.com>
Hi,
2009/11/6 Sverre Rabbelier <srabbelier@gmail.com>:
> This patch adds basic boilerplate support (based on corresponding Perl
> sections) for enabling the building and installation Python scripts.
>
> There are currently no Python scripts being built, and when Python
> scripts are added in future patches, their building and installation
> can be disabled by defining NO_PYTHON.
>
> Signed-off-by: Johan Herland <johan@herland.net>
Does it mean, that it will be possible to write git-<cmd> scripts in
python or, in example, port bash and / or perl scripts to python?
I'm asking because bash+perl is a huge stopper for Windows platform,
which requires basic unix environment to work, while python support
for Windows is excellent and most of Windows developers already use
python.
--
Andrzej
next prev parent reply other threads:[~2009-11-06 23:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 22:52 [PATCH v3 00/12] Reroll of the remote-vcs-helper series Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 01/12] Fix memory leak in helper method for disconnect Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 02/12] Allow programs to not depend on remotes having urls Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 03/12] Use a function to determine whether a remote is valid Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 04/12] Allow fetch to modify refs Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 05/12] Add a config option for remotes to specify a foreign vcs Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 06/12] Allow specifying the remote helper in the url Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 07/12] Add support for "import" helper command Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 08/12] Allow helper to map private ref names into normal names Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 09/12] Allow helpers to report in "list" command that the ref is unchanged Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 10/12] Allow helpers to request the path to the .git directory Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 11/12] Basic build infrastructure for Python scripts Sverre Rabbelier
2009-11-06 22:52 ` [PATCH v3 12/12] Add Python support library for remote helpers Sverre Rabbelier
2009-11-06 23:23 ` Andrzej K. Haczewski [this message]
2009-11-06 23:25 ` [PATCH v3 11/12] Basic build infrastructure for Python scripts Sverre Rabbelier
2009-11-07 12:13 ` Johannes Schindelin
2009-11-06 23:12 ` [PATCH v3 08/12] Allow helper to map private ref names into normal names Daniel Barkalow
2009-11-06 23:19 ` Sverre Rabbelier
2009-11-09 6:42 ` Sverre Rabbelier
2009-11-09 16:44 ` Junio C Hamano
2009-11-09 17:10 ` Sverre Rabbelier
2009-11-09 20:32 ` 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=16cee31f0911061523v5b9754ebg9c846c0e96ac808@mail.gmail.com \
--to=ahaczewski@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=srabbelier@gmail.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).