Jeff King wrote:
On Wed, Oct 25, 2006 at 02:19:15AM -0700, David Rientjes wrote:
No, my criticism is against the added complexity which makes the
modification of git increasingly difficult with every new release. It's a
OK, you seemed to imply problems for end users in your first paragraph,
which is what I was responding to.
_current_ needs. For any experienced shell programmer it is so much
easier to go in and change an option or pipe to a different command or
comment out a simple shell command in a .sh file than editing the C code.
Yes, it's true that some operations might be easier to play with in the
shell. However, does it actually come up that you want to modify
existing git programs? The more common usage seems to be gluing the
plumbing together in interesting ways, and that is still very much
supported.
Indeed. I still use my old git-send-patch script whenever I want to send
patches, simply because I don't like git-send-email and its defaults
much. The interface hasn't changed one bit since I wrote it. That's
pretty stable, since send-patch was created couple of hours before git.c
was submitted to the list, as I wrote the "send-patch" script to send
the patch that did the rewriting.
I'm personally all for a rewrite of the necessary commands in C
("commit" comes to mind), but as many others, I have no personal
interest in doing the actual work. I'm fairly certain that once we get
it working natively on windows with some decent performance, windows
hackers will pick up the ball and write "wingit", which will be a log
viewer and GUI thing for
fetching/merging/committing/reverting/rebasing/sending patches and
whatnot. Possibly it will have hooks to Visual C++ or some other IDE. I
don't know how that sort of thing works, but I'm sure someone clever and
bored enough will want to investigate the possibilities.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html