From: Timo Hirvonen <tihirvon@gmail.com>
To: lukass@etek.chalmers.se
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH 0/8] Make a couple of commands builtin
Date: Wed, 14 Jun 2006 00:54:37 +0300 [thread overview]
Message-ID: <20060614005437.69ff6a62.tihirvon@gmail.com> (raw)
In-Reply-To: <448F1E41.1040607@etek.chalmers.se>
Lukas Sandström <lukass@etek.chalmers.se> wrote:
> This patchseries has the ultimate goal of making
> git-am a builtin.
>
> The version of git-am I'm sending out makes quite heavy
> use of system(), but I think that can be worked around.
> I just haven't figured out how, yet.
I don't think git-stripspace needs to be a built-in. It doesn't even
depend on git. It is just a tiny helper program used by git-am,
git-applymbox, git-commit and git-tag. If all these commands are made
built-in then git-stripspace becomes useless.
--
http://onion.dynserv.net/~timo/
next prev parent reply other threads:[~2006-06-13 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 20:21 [PATCH 0/8] Make a couple of commands builtin Lukas Sandström
2006-06-13 21:54 ` Timo Hirvonen [this message]
2006-06-13 22:03 ` Lukas Sandström
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=20060614005437.69ff6a62.tihirvon@gmail.com \
--to=tihirvon@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=lukass@etek.chalmers.se \
/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).