From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Han-Wen Nienhuys <hanwen@xs4all.nl>, git@vger.kernel.org
Subject: Re: GIT on MinGW problem
Date: Sat, 26 May 2007 23:45:41 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705262343390.4648@racer.site> (raw)
In-Reply-To: <7v4plzi508.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sat, 26 May 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> >> 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!
> > 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 ;-)
> > 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.
>
> > 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
next prev parent reply other threads:[~2007-05-26 22:45 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 1:13 GIT on MinGW problem Aaron Gray
2007-05-12 1:17 ` Junio C Hamano
2007-05-12 2:25 ` Aaron Gray
2007-05-12 3:30 ` Han-Wen Nienhuys
2007-05-25 8:49 ` Johannes Sixt
2007-05-25 9:45 ` Marco Costalba
2007-05-25 10:20 ` Johannes Schindelin
2007-05-25 11:07 ` Johannes Sixt
2007-05-26 19:42 ` Han-Wen Nienhuys
2007-05-26 22:17 ` Johannes Schindelin
2007-05-27 6:56 ` Han-Wen Nienhuys
2007-05-27 10:52 ` Johannes Schindelin
2007-05-27 17:04 ` Han-Wen Nienhuys
2007-05-28 16:54 ` Nix
2007-05-27 20:44 ` Han-Wen Nienhuys
[not found] ` <Pine.LNX.4.64.0705272213350.4648@racer.site>
[not found] ` <f329bf540705271417k1874c1f2u3acc98dc25e058b9@mail.gmail.com>
2007-05-27 21:26 ` Johannes Schindelin
2007-05-25 21:37 ` Aaron Gray
2007-05-26 19:41 ` Han-Wen Nienhuys
2007-05-26 22:26 ` Johannes Schindelin
2007-05-26 22:39 ` Junio C Hamano
2007-05-26 22:45 ` Johannes Schindelin [this message]
2007-05-26 22:53 ` Han-Wen Nienhuys
2007-05-26 23:47 ` Jakub Narebski
2007-05-27 6:30 ` Han-Wen Nienhuys
2007-05-27 6:39 ` Shawn O. Pearce
2007-05-27 7:02 ` Han-Wen Nienhuys
2007-05-27 7:21 ` Steven Grimm
2007-05-27 9:09 ` Jakub Narebski
2007-05-27 23:18 ` Han-Wen Nienhuys
2007-05-28 0:04 ` Johannes Schindelin
2007-05-28 0:31 ` Han-Wen Nienhuys
2007-05-27 10:46 ` Johannes Schindelin
2007-05-27 18:50 ` Han-Wen Nienhuys
2007-05-27 19:52 ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-27 20:39 ` Aaron Gray
2007-05-27 21:19 ` Han-Wen Nienhuys
2007-05-27 21:24 ` Aaron Gray
2007-05-27 21:39 ` Aaron Gray
2007-05-27 21:55 ` Han-Wen Nienhuys
2007-05-27 22:22 ` Aaron Gray
2007-05-27 22:28 ` Han-Wen Nienhuys
2007-05-27 22:56 ` GIT on MinGW - No symbolic links support Aaron Gray
2007-05-27 23:56 ` Johannes Schindelin
2007-05-29 7:11 ` Johannes Sixt
2007-05-27 22:22 ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-29 10:54 ` GIT on MinGW problem Johannes Sixt
2007-05-29 11:45 ` Marius Storm-Olsen
2007-05-29 12:10 ` Johannes Sixt
2007-05-29 14:29 ` Han-Wen Nienhuys
2007-05-29 14:49 ` Johannes Sixt
2007-05-29 12:11 ` Johannes Schindelin
2007-05-29 13:05 ` Marius Storm-Olsen
2007-05-29 13:24 ` Johannes Sixt
2007-05-29 14:36 ` Marius Storm-Olsen
2007-05-29 13:47 ` Johannes Schindelin
2007-05-29 14:13 ` Johannes Sixt
2007-05-29 15:28 ` Nguyen Thai Ngoc Duy
2007-05-29 15:47 ` Johannes Sixt
2007-05-29 18:45 ` Nguyen Thai Ngoc Duy
2007-05-30 3:03 ` [PATCH] Make git-k an alias to gitk Johannes Schindelin
2007-05-30 7:06 ` Johannes Sixt
2007-05-30 2:16 ` GIT on MinGW problem Han-Wen Nienhuys
2007-05-30 2:39 ` Johannes Schindelin
2007-05-30 2:57 ` Shawn O. Pearce
2007-05-30 3:25 ` [PATCH] Git wrapper: add --redirect-stderr option Johannes Schindelin
2007-05-30 3:38 ` Shawn O. Pearce
2007-05-30 3:45 ` Johannes Schindelin
2007-05-30 3:53 ` Shawn O. Pearce
2007-05-30 4:12 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2007-05-12 14:20 GIT on MinGW problem Aaron Gray
[not found] ` <033501c79710$a2eb0290$0200a8c0@AMD2500>
2007-05-15 19:51 ` Han-Wen Nienhuys
2007-05-16 8:02 ` Johannes Sixt
2007-05-21 18:22 ` Nguyen Thai Ngoc Duy
2007-05-26 23:08 ` Han-Wen Nienhuys
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=Pine.LNX.4.64.0705262343390.4648@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=junkio@cox.net \
/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).