From: Richard Ipsum <richard.ipsum@codethink.co.uk>
To: git@vger.kernel.org
Subject: Dependency query regarding contrib scripts
Date: Tue, 1 Dec 2015 16:52:10 +0000 [thread overview]
Message-ID: <20151201165209.GA28230@salo> (raw)
Hi,
Having read the docs for integrating new subcommands into git[1] I am looking
for some clarification of the following,
"While we strongly encourage coding in portable C for portability,
these [C, shell, perl] specific scripting languages are also acceptable.
We won’t accept more without a very strong technical case,
as we don’t want to broaden the Git suite’s required dependencies"
Does this also mean that use of non-core modules by, for example, perl scripts,
is out of the question for contrib scripts? Or is it acceptable but ideally
minimised?
In particular I'd like to be able to make use of Git::Raw[2] and also ideally
the Moo framework[3].
Thanks,
Richard Ipsum
[1]: ftp://www.kernel.org/pub/software/scm/git/docs/v2.4.0/howto/new-command.html
[2]: http://search.cpan.org/~jacquesg/Git-Raw-0.58/lib/Git/Raw.pm
[3]: http://search.cpan.org/~haarg/Moo-2.000002/lib/Moo.pm
next reply other threads:[~2015-12-01 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 16:52 Richard Ipsum [this message]
2015-12-01 20:52 ` Dependency query regarding contrib scripts 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=20151201165209.GA28230@salo \
--to=richard.ipsum@codethink.co.uk \
--cc=git@vger.kernel.org \
/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).