On Jan 19, 2008, at 11:42 PM, Johannes Schindelin wrote:
Hi,
On Sat, 19 Jan 2008, Steffen Prohaska wrote:
On Jan 14, 2008, at 10:40 PM, Johannes Schindelin wrote:
FWIW I think that we are stable enough already to have
better-than-preview releases (although, like I said, lack of
git-svn is a reason for me not to declare non-beta status yet).
Currently, we install git-svn even that we know it won't work. This
is certainly not the type of installer I'd like to declare beta.
Maybe we could clearly state what we have and exclude all commands
that do not work from the installer. If we only installed stable
commands and give a clear indication on the perspective for the
missing commands, maybe we could do a beta release for plumbing and
core porcelain. The commands that are not ready would still be
included in msysgit. So it would be easy for developers to get and
improve what we already have. But end users would not see commands
that do not work.
That sounds good.
These are the programs that do not work, AFAICT:
- cvsexportcommit
- cvsimport
- send-email
- svn
I pushed work/install-fewer to msysgit, which excludes the
following commands:
git-cvsexportcommit
git-cvsimport
git-cvsserver
git-send-email
git-shell.exe
git-svn
This patch looks good, except that it calls "egrep", which is a simple
script to call "grep -E", so I would like the patch to be more
explicit
and call "grep -E" right away. Or even better: "grep", since it
does not
even start to begin using extended regular expressions.
I'll check this. My first "grep" didn't work. Maybe I need
'\|' instead of a simple '|'. I'll find out.
The next list contains commands that I am not sure about.
Should we install these?
git-archimport
Agree; we do not ship tla.
git-help--browse
AFAICT we need it, and probably need to adjust it to msysGit (although
that might not be necessary; I have no time to look into it).
Do you mean it is needed for "git help"? I don't think so.
We launch the HTML browser directly using the Windows API
and do not support man.
git-instaweb
Agree; we do not ship apache or lighttp.
git-mailinfo.exe
git-mailsplit.exe
AFAIR these are needed for git-am.
I'll check.
git-quiltimport
Even if we do not ship quilt, this script might be useful; it does
not use
quilt itself.
Will include it.
git-relink
This is not really useful, I think, but it _should_ work on
Filesystems
that support hard links, so IMHO we sould ship it.
ditto.
The last list contains commands that I think should be installed:
git-citool
AFAICT this is not built anymore by git.git.
I ran "rm /bin/git*" and did a fresh install. I'll check
again.
If it is still built, I'll exclude it from the installer.
git-filter-branch
I recently tried to use filter-branch on Windows, but it did not
work, so
I resorted to Linux, where the same command line worked.
So I vote to exclude it until it starts to work properly (although
I think
that the tests pass).
Or maybe somebody else should confirm that it actually works with a
simple
msg-filter to transform msysgit's "devel" branch (which was my non-
working
test case).
I'll exclude it.
git-gui
git-gui.tcl
Do we really need both? Or is the second just a left-over from an old
install?
dunno, will check.
git-mergetool
I think we need to include a tool like tkdiff for this to become
actually
useful, or exclude it from the distribution.
This is pretty useful. I use it regularly. You can point
mergetool.<tool>.path to the tool of your choice (e.g.
kdiff3 or ecmerge) and use git-mergetool right away.
Steffen
