From: Steffen Prohaska <prohaska@zib.de>
To: Torgil Svensson <torgil.svensson@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: git on Cygwin: Not a valid object name HEAD
Date: Sat, 11 Aug 2007 02:43:54 +0200 [thread overview]
Message-ID: <EF7DFA5A-9C3A-4D0B-9533-D1D60AE4A44C@zib.de> (raw)
In-Reply-To: <e7bda7770708101531n782118e9qb9c6de4e934940ea@mail.gmail.com>
On Aug 11, 2007, at 12:31 AM, Torgil Svensson wrote:
> On 8/10/07, Steffen Prohaska <prohaska@zib.de> wrote:
>
>> [..list of tools and links]
>
> Thank you for the information! i'll check those up.
I hope to have an improved list on monday, sorted by priority of
the developers I'm working with.
I thought I do some coding, to find out a bit more about the
stability of msysgit. So I started and added support for kdiff3
on Windows (see patches in separate mail).
I'm impressed. Pretty much everything I tried today worked for
me. After I got git gui running, and learned how to avoid pitfalls
of git submodule, development went smoothly. I pushed and pulled a
bit from linux and mac and did some coding. Thanks for the vim
setup!
I think you (and more people I don't yet know) did a great job
with msysgit. I'd recommend it over cygwin's git, which caused
some trouble for me.
Thanks!
>>>> My goal would be to type 'make windist' in the official repo and
>>>> get a very basic installer (maybe just a zip archive) that contains
>>>> everything needed to run git on Windows. Unpacking this self-
>>>> contained
>>>> installer on a freshly installed Windows should get you going.
>>>> There
>>>> should be no need to install Cygwin or something else.
>>>>
>>>> Is this realistic?
>>>> What is needed to get there?
>>>> What would be an estimated timeframe to achieve this goal?
>>>>
>>>> Will all this run on Windows XP 64 bit and Windows Vista 64 bit?
>>>
>>> How fast can you type?
>>
>> I don't see your point. The question is if git runs flawlessly
>> on 64 bit systems, which we use for development. I have no experience
>> with mingw. Maybe there are some issues with 64 bit Windows, maybe
>> not. But its a reasonable question?
>>
>>> Why does it have to be the _official_ repo? Git have submodule
>>> support, so you could do a repo called
>>> "my_excellent_git_environment_for_windows.git" and have the official
>>> repo as submodule (msysgit is done this way).
>>
>> The official repo would indicate a real commitment to me that
>> Windows support if officially maintained.
>
> I agree it's reasonable questions. My point is that to get something,
> you have to be active (and you're a prime example of that I think).
>
> Quoted from http://git.or.cz/ : "Traditionally, the low-level part of
> Git is called plumbing and the interfaces and frontends are called
> porcelains. Git itself comes with a default porcelain bundled and that
> is actually what you will normally mean when you say you use Git."
>
>
> What do you include in the "make windist" installer and the "Windows
> support" ? Are you talking porcelain or plumbing?
Hard to say. I believe now, from what I learned today, that the msysgit
approach is quite reasonable: Grouping all needed unix tools around a
submodule containing git. But the submodule should be git.git. I think
this is what I'd expect. I like the idea of bringing everything needed
along, and keeping it separate from the rest of the system. This avoids
conflicts with, for example, cygwin.
I don't think I would expect much more for a basic setup. All tests
should run, maybe some msysgit tests would be needed to test the
pitfalls
we'll discover; maybe not. I'll test XP 64 bit and Vista 64 bit
beginning
of next week. Getting started hacking msysgit could be a bit easier.
I didn't like the submodule problems I ran into and I still didn't find
out how to push to the git mob branch.
For me a next step would be do some polishing. For example tune
git to integrate with other Windows tools, like what I proposed for
git-mergetool. I really started to love git when it launched a
graphical mergetool automatically for me. After that point I never
edited merge markers again. Things I needed too much time before are
now running so smoothly. I think such a tight integration is really
useful to convince people. I'd also expect default choices to be
reasonable. I'm not yet 100% sure, but my feeling it that core.autocrlf
should be set to true by default on Windows, globally. A bit more
of msysgit specific documentation would also be good. Maybe we should
add a platform specific section to the user-manual. How could help
in msysgit be handled? By a Windows help document?
I could also think of a fail safe update, that allows to upgrade an
existing msysgit to a specific tag (maybe after stashing the current
installation and reverting in case of problems).
Maybe git gui could be integrated with the Windows Explorer and be
launched on a directory. Maybe this is one of your evil plans. But
this is already more than I need.
Back to the basic stuff.
What do you think is needed to merge changes back to git.git?
I counted approximately 20k diff lines (incl. context) between msysgit's
git master and git.git's master. At a first glance much of them seem to
be compatibility stuff.
Steffen
next prev parent reply other threads:[~2007-08-11 0:43 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 9:02 git on Cygwin: Not a valid object name HEAD Sebastian Schuberth
2007-08-07 11:58 ` Johannes Schindelin
2007-08-07 12:13 ` Sebastian Schuberth
2007-08-07 13:18 ` Sebastian Schuberth
2007-08-07 14:36 ` Shawn O. Pearce
2007-08-07 14:58 ` Brian Downing
2007-08-07 15:27 ` Sebastian Schuberth
2007-08-07 17:11 ` Steffen Prohaska
2007-08-07 17:42 ` Mark Levedahl
2007-08-07 19:41 ` Steffen Prohaska
2007-08-07 21:44 ` Linus Torvalds
2007-08-07 22:28 ` Junio C Hamano
2007-08-08 3:47 ` Linus Torvalds
2007-08-07 22:46 ` Steffen Prohaska
2007-08-07 22:49 ` [PATCH] cygwin: added fopen "b" and open O_BINARY to support cygwin's textmode Steffen Prohaska
2007-08-07 22:49 ` [PATCH] tests: added d2u to have unix style testfiles even in textmode Steffen Prohaska
2007-08-08 3:03 ` Linus Torvalds
2007-08-08 5:00 ` Steffen Prohaska
2007-08-07 23:20 ` git on Cygwin: Not a valid object name HEAD Steffen Prohaska
2007-08-08 4:25 ` Brian Downing
2007-08-08 5:46 ` Steffen Prohaska
2007-08-07 22:26 ` Junio C Hamano
2007-08-08 7:55 ` Sebastian Schuberth
2007-08-08 13:50 ` Mark Levedahl
2007-08-08 15:51 ` Steffen Prohaska
2007-08-08 16:41 ` Mark Levedahl
2007-08-08 17:20 ` Johannes Schindelin
2007-08-08 19:37 ` Steffen Prohaska
2007-08-08 20:13 ` Steffen Prohaska
2007-08-08 20:36 ` Steffen Prohaska
2007-08-08 23:07 ` Mark Levedahl
2007-08-09 4:59 ` Steffen Prohaska
2007-08-09 6:01 ` Marius Storm-Olsen
2007-08-09 6:38 ` Steffen Prohaska
2007-08-09 6:47 ` Marius Storm-Olsen
2007-08-09 8:50 ` Johannes Schindelin
2007-08-09 9:00 ` Marius Storm-Olsen
2007-08-09 10:33 ` Steffen Prohaska
2007-08-08 21:30 ` Johannes Schindelin
2007-08-09 6:20 ` Steffen Prohaska
2007-08-10 6:07 ` Torgil Svensson
2007-08-10 7:19 ` Steffen Prohaska
2007-08-10 10:30 ` Johannes Schindelin
2007-08-10 11:14 ` Steffen Prohaska
2007-08-10 22:31 ` Torgil Svensson
2007-08-11 0:43 ` Steffen Prohaska [this message]
2007-08-13 10:50 ` Johannes Schindelin
2007-08-15 0:04 ` Torgil Svensson
2007-08-15 5:22 ` Steffen Prohaska
2007-08-15 5:30 ` David Kastrup
2007-08-15 5:43 ` Steffen Prohaska
2007-08-15 6:59 ` David Kastrup
[not found] ` <86k5rx474o.fsf@lola.quinscape.zz>
2007-08-15 7:38 ` Shawn O. Pearce
2007-08-15 12:42 ` Mark Levedahl
2007-08-15 12:48 ` Mark Levedahl
2007-08-15 13:06 ` Steffen Prohaska
2007-08-16 0:27 ` Mark Levedahl
2007-08-16 6:04 ` Steffen Prohaska
2007-08-16 11:55 ` Mark Levedahl
2007-08-07 15:29 ` Mark Levedahl
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EF7DFA5A-9C3A-4D0B-9533-D1D60AE4A44C@zib.de \
--to=prohaska@zib.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=torgil.svensson@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).