From: "Ameer Armaly" <ameerarmaly@bellsouth.net>
To: "Junio C Hamano" <junkio@cox.net>, <git@vger.kernel.org>
Cc: "Nick Hengeveld" <nickh@reactrix.com>
Subject: Re: More Porcelains?
Date: Mon, 26 Sep 2005 20:57:33 -0400 [thread overview]
Message-ID: <000a01c5c2fe$71fd6200$0200a8c0@AMEER> (raw)
In-Reply-To: 7v64sn8hml.fsf_-_@assigned-by-dhcp.cox.net
----- Original Message -----
From: "Junio C Hamano" <junkio@cox.net>
To: <git@vger.kernel.org>
Cc: "Nick Hengeveld" <nickh@reactrix.com>
Sent: Monday, September 26, 2005 8:43 PM
Subject: More Porcelains?
> Nick Hengeveld <nickh@reactrix.com> writes:
>
>> Good point - use of environment variables is more consistent. Use of
>> command-line arguments is a bit more convenient in my case since I'm
>> driving the transfer from a perl script, but I suppose consistency is
>> more important...
>
> Now you made me curious.
>
> How many of you are working on your own Porcelains, announced or
> unannounced? I know about Cogito and StGIT ;-). In a distant
> past I have heard of something called JIT but I think it is now
> defunct. Matthias Urlichs said he is doing something with
> Python. Anybody else?
>
I am seriously looking at putting one together in the D language
(http://www.digitalmars.com/d) <plug>, though it doesn't actually do
anything as of yet, since I have to balance classes along with it.
>
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-09-27 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 17:51 [PATCH 1/3] Support for SSL client cert Nick Hengeveld
2005-09-26 18:23 ` Petr Baudis
2005-09-26 18:36 ` Nick Hengeveld
2005-09-26 20:43 ` Junio C Hamano
2005-09-27 0:15 ` Nick Hengeveld
2005-09-27 0:43 ` More Porcelains? Junio C Hamano
2005-09-27 0:57 ` Ameer Armaly [this message]
2005-09-27 6:15 ` Daniel Barkalow
2005-09-27 8:16 ` Catalin Marinas
2005-09-27 17:02 ` Mariano Videla
2005-09-28 11:30 ` Vincent Hanquez
2005-09-28 20:22 ` Matthias Urlichs
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='000a01c5c2fe$71fd6200$0200a8c0@AMEER' \
--to=ameerarmaly@bellsouth.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nickh@reactrix.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).