Re: GIT on MinGW problem

Johannes Schindelin [off-list ref] writes:

quoted

In this, part of the pain is that Git tries to guess the version number
by itself in a complicated way.

Yes, I never understood that myself why it has to be so complicated. But 
then, it did not make _my_ life hard, so I did not care.

"echo "MyVersionNumber" >version && make"?

OTOH, it _is_ a nice thing to protohype the new commands as shell or perl 
scripts. When they stabilize enough, convert them to builtins.

Protohype is a nice word.  Throw out a half-working stuff and
advertise it as the best thing since sliced bread even before it
starts to being useful ;-)

There are exactly 4 perl scripts left that I regularly use:

add--interactive, cvsimport, remote and svn.

I somehow have the feeling that it is not worth the effort to convert 
cvsimport and svn. With add--interactive, I think it's better to leave it 
as is before Junio goes on another "what have I done? why did I have to 
add _this_?" spree.

I do not follow you here.

But remote will soon be the center of my crosshairs.

I am afraid that it might be a bit premature.

I've been hoping that we can make git-clone a thin wrapper
around init/remote/fetch/checkout.  For one thing, we would want
to split the separate-remotes layout and bareness to create
"mirror" (I called it "pure" previously, but this is really a
mirror) layout for git-clone, among other things, and that kind
of enhancements would need to be done inside git-remote.

Hi,

On Sat, 26 May 2007, Junio C Hamano wrote:

Johannes Schindelin [off-list ref] writes:

quoted

quoted

In this, part of the pain is that Git tries to guess the version number
by itself in a complicated way.

Yes, I never understood that myself why it has to be so complicated. But 
then, it did not make _my_ life hard, so I did not care.

"echo "MyVersionNumber" >version && make"?

Good to know!

quoted

OTOH, it _is_ a nice thing to protohype the new commands as shell or perl 
scripts. When they stabilize enough, convert them to builtins.

Protohype is a nice word.  Throw out a half-working stuff and
advertise it as the best thing since sliced bread even before it
starts to being useful ;-)

It started out as a typo. But then I liked it so much that I kept it ;-)

quoted

With add--interactive, I think it's better to leave it [...]

I do not follow you here.

You mentioned several times that you were unsure if add--interactive was a 
good idea. But I like it very much.

quoted

But remote will soon be the center of my crosshairs.

I am afraid that it might be a bit premature.

I've been hoping that we can make git-clone a thin wrapper
around init/remote/fetch/checkout.  For one thing, we would want
to split the separate-remotes layout and bareness to create
"mirror" (I called it "pure" previously, but this is really a
mirror) layout for git-clone, among other things, and that kind
of enhancements would need to be done inside git-remote.

Fair enough.

Ciao,
Dscho