From: Sverre Rabbelier <srabbelier@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>,
Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH] Improve documentation for git-remote-helpers
Date: Mon, 22 Mar 2010 00:35:38 +0100 [thread overview]
Message-ID: <fabb9a1e1003211635w27f0b22em73c7c6431c3998af@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1003211907390.14365@iabervon.org>
Heya,
On Mon, Mar 22, 2010 at 00:29, Daniel Barkalow <barkalow@iabervon.org> wrote:
> Yup. Or maybe these should be documented as a list of capabilities which
> mean that the helper supports the command with the same name, since that's
> a common pattern, and documenting it as a pattern makes it obvious that,
> if we have a new 'export' command, and it needs a capability, it'll fit
> the pattern.
Speaking of which, I have uploaded a preliminary version of the export
capability to my github repository [0] since Ramkumar wanted to have a
look at it. Sadly I have not been able to test it yet, I wanted to
work on that today but instead spent hours on getting the first
argument to the helper to be 'origin' (or whatever the user sets it to
with the --origin option), something that's been bothering me forever.
No documentation yet though, working on that ;).
[0] http://github.com/SRabbelier/git
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-03-21 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 17:26 [PATCH] Improve documentation for git-remote-helpers Ramkumar Ramachandra
2010-03-21 18:21 ` Ramkumar Ramachandra
2010-03-21 23:29 ` Daniel Barkalow
2010-03-21 23:35 ` Sverre Rabbelier [this message]
2010-03-22 0:06 ` Daniel Barkalow
2010-03-22 15:40 ` Sverre Rabbelier
2010-03-22 7:28 ` Ramkumar Ramachandra
2010-03-22 3:04 ` Ramkumar Ramachandra
2010-03-22 3:38 ` Ramkumar Ramachandra
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=fabb9a1e1003211635w27f0b22em73c7c6431c3998af@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).