From: Jakub Narebski <jnareb@gmail.com>
To: "Edward Z. Yang" <ezyang@MIT.EDU>
Cc: "René Moser" <mail@renemoser.net>, git <git@vger.kernel.org>
Subject: Re: git-ftp for /contrib
Date: Thu, 27 May 2010 17:54:02 -0700 (PDT) [thread overview]
Message-ID: <m3r5kwrgjz.fsf@localhost.localdomain> (raw)
In-Reply-To: <1275000359-sup-1204@ezyang>
"Edward Z. Yang" <ezyang@MIT.EDU> writes:
> Excerpts from René Moser's message of Thu May 27 15:19:43 -0400 2010:
> >
> > I scripted a small tool called git-ftp for optimal interaction between
> > git and ftp. I use it quite often and I thought it might fit in the
> > contrib section of git.
> >
> > Please have a look at http://github.com/resmo/git-ftp and give me some
> > feedback. See README and an (almost outdated) screencast.
>
> What a coincidence! I've also made a small Python script for git<->ftp
> synchronization, unsurprisingly called the same thing.
>
> http://github.com/ezyang/git-ftp
>
> (Unfortunately, since it's written in Python it seems pretty unlikely
> to go into the contrib section of git.)
I don't know about adding this script to contrib/ section (you would
probably need to send properly formatted patch adding it in approriate
place in contrib/), but could each of you add your project to the
http://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools
page on Git Wiki? Thanks in advance.
P.S. I wonder how hard would be to add native support for "dumb"
ftp:// protocol, so that "git fetch ftp://example.com/repo.git"
_and_ "git push ftp://example.com/repo.git" works.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-05-28 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 19:19 git-ftp for /contrib René Moser
2010-05-27 22:46 ` Edward Z. Yang
2010-05-28 0:54 ` Jakub Narebski [this message]
2010-05-28 1:49 ` Ilari Liusvaara
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=m3r5kwrgjz.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=ezyang@MIT.EDU \
--cc=git@vger.kernel.org \
--cc=mail@renemoser.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).