"Marco Costalba" <mcostalba@gmail.com> writes:

quoted text
>> That's a true point. Altough if git 1.5 ships _without_ '--refresh'
>> option in 'git runstatus' for a porcelain tool point of view it means
>> *do forget* that option until next major release. There's no point in
>> adding the feature one day after git 1.5 is out; qgit will not use
>> that feature anyway for next months.
>
> I could opt for shipping qgit 1.5.5 _without_ using '--refresh' and
> then ship, as example in a month, qgit 1.5.6 that uses the feaure. But
> I can do this _only_ if git 1.5 has it.

You can run it once when you start up to see if --refresh is
supported with the git the user has, and keep that result
throughout the life of the qgit process (so you have to do the
check only once).

What would you do when working with older git anyway?  You would
need to fall back on some code -- or would you require a certain
version of git to go with this version of qgit?

About "Cygwin and Linux NTFS seem to disagree with lstat(2)"
problem.  Is it really what is happening here?  It might be an
interesting exercise to printf(3) the struct stat members in
both environments and find out where they disagree.  It might
turn out to be something trivial to fix for the filesystem guys.
I am not personally interested in solving that problem myself
(nor I am equipped to -- I do not have ready access to dual
booting Windows setup), but still it is interesting to find out
what the issue is.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html