From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Mike Ralphson <mike.ralphson@gmail.com>,
Marek Zawirski <marek.zawirski@gmail.com>,
git@vger.kernel.org
Subject: Re: [JGIT PATCH 1/1] jgit: create a tag command
Date: Fri, 11 Jul 2008 10:28:32 +0200 [thread overview]
Message-ID: <200807111028.32973.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20080711020507.GD31862@spearce.org>
fredagen den 11 juli 2008 04.05.07 skrev Shawn O. Pearce:
> Mike Ralphson <mike.ralphson@gmail.com> wrote:
> >
> > Loving the make_jgit stuff.
>
> So making jgit a single stand-alone, portable shell script for
> command line usage was a good idea? ;-)
>
> I think we are at the point where we need to either write a
> #@!*(!@(! command line option parser, import one, or stop writing
> command line programs. I would certainly appreciate any opinion
> you might have on the matter.
I've come to that conclusion too, but not yet to the code :)
-- robin
next prev parent reply other threads:[~2008-07-11 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 22:41 [JGIT PATCH 1/1] jgit: create a tag command Robin Rosenberg
2008-07-06 23:16 ` Robin Rosenberg
2008-07-10 15:31 ` Mike Ralphson
2008-07-10 18:02 ` Robin Rosenberg
2008-07-11 10:50 ` Differences between git-applu and GNU patch (was: [JGIT PATCH 1/1] jgit: create a tag command) Jakub Narebski
2008-07-11 2:05 ` [JGIT PATCH 1/1] jgit: create a tag command Shawn O. Pearce
2008-07-11 8:28 ` Robin Rosenberg [this message]
2008-07-11 8:45 ` Mike Ralphson
2008-07-12 3:01 ` Shawn O. Pearce
2008-07-12 3:42 ` Shawn O. Pearce
2008-07-17 21:31 ` Robin Rosenberg
2008-07-17 21:45 ` Shawn O. Pearce
2008-07-17 22:24 ` Robin Rosenberg
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=200807111028.32973.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=marek.zawirski@gmail.com \
--cc=mike.ralphson@gmail.com \
--cc=spearce@spearce.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).