Thats true for linux too. /a/b/c and /a/b/c can be 2 totally different files depending on the vfs namespace you are one. cu, michael -- It's already too late! -

Hi, Aha. So to support Windows, we have to wrap all sites that use that So to support Windows, we have to special case having a ":" as second Yes, but there are still incompatibilities with POSIX. Again, when you did not close the file, you cannot delete (or rename) it. So, to support Windows, ... All this supporting Windows business is certainly possible, if tedious. Ciao, Dscho -

50. What could be improved on the GIT homepage? TO DO 171 / 683 non-empty responses -- Note from the homepage, http://git.or.cz/ This website itself is tracked in Git as well - you can browse its development history or even clone it from http://repo.or.cz/r/git-homepage.git. The site is covered by GPLv2 and maintained by Petr Baudis who always takes patches eagerly. ;-) -- List of answers, without count, divided into broad categories. Some answers were hard to classify into one sectio...

Thanks for your reply. I'll have to admit that I overlooked the hint for "the asciidoc/xmlto toolchain" because it was in a separate paragraph instead of another item in the system requirements enumeration. (The tool's version number does not look promising so far.) I rebuilt Git on my system because I was notified that a newer release became available. Regards, Markus

It is sort of possible. Without cygwin he'll be in the black for the few features that are still implemented as shell-scripts, but perhaps he/she qgit is possible to use natively, if one installs the qgit4 libraries for windows, but it's more of a viewer than an action gui. git-gui and gitk are usable if you have the windows TCL port. I haven't tried it, but there are installers available, so testing it out (with all dependencies) When someone gets around to doing it ;-) For a real answer, I'...

Oh? I didn't know that. Windows and its unixifying toolboxes is unknown Yes, my phrasing there was a bit obscure. I meant that all dependencies I was under the impression that the windows port suffers from Windows' lack of a proper fork() and friends and that a proper library would help solving those problems. Perhaps I was misinformed. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-...

Re "functional". Have to remind something (besides the fork): Filesystem: - no proper VFS (can't do anything with files opened elsewhere, and we have not enough error handling and diagnostic output to detect the problems) - no proper filename semantics (case-insensitivity and stupid rules for allowed characters in filenames, like ":" in filenames in cross-platform projects) - no acceptable level of performance in filesystem and VFS (readdir, stat, open and read/write are annoyin...

The MS exec* calls just concatenate all of the argv arguments, separating them with a space into a single buffer. Look at the general _exec* page: http://msdn2.microsoft.com/en-us/library/431x4c1w(VS.80).aspx and read the first "Note" section. If you know what the library on the other end is doing to re-parse the arguments back into separate strings, it might be possible to quote things enough to handle names with spaces, but it is hard. David -

That's a 20-20 hindsight: if you deliberately write a program to rely heavily on Posix-isms, don't be surprised when you discover that it I'm not sure what you are talking about. What VFS do you use on There's a flag on Windows to open files case-sensitively, if you need that. In any case, I don't see how this can be of any real relevance to porting GIT. As for ":" in file names, simply don't use it, like you don't use white space or characters below 32 decimal: it's With what libraries? ...

Hi, The problem is that on Windows, you cannot keep a file open and delete it at the same time. This is an issue in Windows' equivalent of VFS. A neat trick to work with temporary files without permission issues is to open the file and delete it right after that. This does not work on The problem is not so much opening, but determining if an existing file and a file in the index have the same name. For example, "README" in the index, but "readme" in the working directory, will be ha...

qgit-2.0 works natively under Windows http://sourceforge.net/project/showfiles.php?group_id=139897 Check the README for how to install. Marco -

It is not crashing. It is just not handling unexpected situation properly: $ testcase.sh ... Switched to branch "foo" CONFLICT (delete/modify): file1 deleted in HEAD and modified in master. Version master of file1 left in tree. Automatic merge failed; fix conflicts and then commit the result. fatal: internal error: ce_mode is 0 $ git ls-files --cached --stage 100644 72139f38953679bd19b3a7938c479d73c1aa7b59 1 file1 100644 3181f904ce3f9364b08524edd262a7a...

FWIW, backtrace. I'm giving up for today. Anyone? (gdb) bt #0 0x080b6ac5 in die_builtin (err=0x80f3b92 "internal error: ce_mode is %o", params=0xbfd91c34 "") at usage.c:24 #1 0x080b6b84 in die (err=0x80f3b92 "internal error: ce_mode is %o") at usage.c:76 #2 0x080a3883 in ce_match_stat_basic (ce=0xb7f6a00c, st=0xbfd91cb8) at read-cache.c:153 #3 0x080a398f in ie_match_stat (istate=0x81342e0, ce=0xb7f6a00c, st=0xbfd91cb8, options=0) at read-cache.c:208 #4 0x080c87f3 in reus...

Then, how do I search for a good version with git bisect if I only have the one data-point "master is bad"? All I tried when testing those 5 versions was trying to find a good version so that I can actually do an automatic bisect. And I stopped at 1.5.3 because I figured that my test-case is probably just pretty uncommon and was basically always broken. Another manual "bisect" shows that 1.5.0 also crashes and as 1.4.0 doesn't even want to read my git git repository, I don't intend to go even ...

OK, using that approach, I bisected it, and even found a "guilty" commit, although it is pretty much useless: 1cfe77333f274c9ba9879c2eb61057a790eb050f is first bad commit commit 1cfe77333f274c9ba9879c2eb61057a790eb050f Author: Junio C Hamano <junkio@cox.net> Date: Tue Jan 30 01:11:08 2007 -0800 git-blame: no rev means start from the working tree file. Warning: this changes the semantics. This makes "git blame" without any positive rev to start digging from the work...

It's not a "bisect" when it crashes in all versions. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum -

Also fix "bisect bad" and "bisect good" short usage description. Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- Documentation/git-bisect.txt | 19 +++++++++++++++++-- 1 files changed, 17 insertions(+), 2 deletions(-) diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index 1072fb8..2be2284 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -16,8 +16,9 @@ The command takes various subcommands, and different options depend...

Hi, Maybe it is time to have a special exit status for "dunno"? But this is not something to fix in your patch, just an idea for a future patch. Ciao, Dscho -

Also use "die" instead of "echo >&2 something ; exit 1". And simplify "bisect_replay". Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- git-bisect.sh | 46 +++++++++++++--------------------------------- 1 files changed, 13 insertions(+), 33 deletions(-) diff --git a/git-bisect.sh b/git-bisect.sh index 847250c..e12125f 100755 --- a/git-bisect.sh +++ b/git-bisect.sh @@ -106,12 +106,11 @@ bisect_start() { die "'$arg' does not appear to be a valid revision"...

Good catch, I've amended the commit and replaced q/cc/bisect-dunno with this series. -- larsh -

Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- git-bisect.sh | 46 ++++++++++++++++++++-------------------------- 1 files changed, 20 insertions(+), 26 deletions(-) diff --git a/git-bisect.sh b/git-bisect.sh index 94534e6..847250c 100755 --- a/git-bisect.sh +++ b/git-bisect.sh @@ -108,9 +108,9 @@ bisect_start() { } if [ $bad_seen -eq 0 ]; then bad_seen=1 - bisect_write_bad "$rev" + bisect_write 'bad' "$rev" else - bisect_write_good "$re...

Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- git-bisect.sh | 17 ++++++++--------- 1 files changed, 8 insertions(+), 9 deletions(-) diff --git a/git-bisect.sh b/git-bisect.sh index 388887a..436ccf6 100755 --- a/git-bisect.sh +++ b/git-bisect.sh @@ -64,7 +64,7 @@ bisect_start() { branch=`cat "$GIT_DIR/head-name"` else branch=master - fi + fi git checkout $branch || exit ;; refs/heads/*) @@ -95,11 +95,11 @@ bisect_start() { ...

--bisect-all is still missing a Documentation/ patch. Gruesse, -- Frank Lichtenheld <frank@lichtenheld.de> www: http://www.djpig.de/ -

Hi, Thanks for doing this. I think that especially the factorisation adds tremendously to the readibility. Ciao, Dscho -

"undecided"? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum -