Clifford Caoile said the following on 25.06.2008 10:02:
Hi:
On Wed, Jun 25, 2008 at 4:09 PM, Marius Storm-Olsen <[EMAIL PROTECTED]> wrote:
Steffen Prohaska said the following on 24.06.2008 21:53:
For a six liner such as git.cmd, the simpler solution were to not
touch echo state at all and prefix all commands by @.
This sounds like a reasonable way to handle this, although I must admit
that I have *no* idea how Windows bat scripts work. If
someone pushes a fix to the mob branch, I'll take it.
How about gitk.cmd?
Ok, I just pushed
http://repo.or.cz/w/msysgit.git?a=commitdiff;h=298b1478ab28e529a1d277c9be2b994e2f0222fa
to the mso/silence_cmd branch. Just merge and kill the branch.
I have no problem with silencing the cmd file.
However, are you sure this branch is based on a recent branch? For
example, the PATH addition [1] to these files is not in your
commitdiff.
Also, you should probably give a shout out by adding to the commit
message "Suggested-by: Stephan Hennig" and "Suggested-by: Roman
Terekhov"
Clifford,
You are of course right. Repushed a fixed up commit:
http://repo.or.cz/w/msysgit.git?a=commitdiff;h=229a38207aea845b7bc37d27f13d1db7f45da82e
/me smacks self for working on an old devel branch.. *sic*
--
.marius
