Hi,

On Fri, 29 Feb 2008, Marius Storm-Olsen wrote:

quoted text
> I just caught a glimpse of the '.git file' efforts, as a file for 
> redirection to a real repository.
> 
> As far as I can tell, the reason for adding the support is to in the end 
> provide a cross-platform way of supporting workdirs. (If this is not the 
> [main] point, please point me to the thread describing the real reason, 
> I couldn't find it.)

This is the main reason, yes.

However, you can also use the .git file to separate the working directory 
from the repository, say, on two different drives, when you do not have 
symbolic links.

quoted text
> However, wouldn't simply redirecting everything into a real repo then 
> create problems with shared index file and more? A problem which could 
> be tacled by file suffixes or other methods, I'm sure, but which would 
> require even more patches to achieve the goal.

Not only would it requre these patches, but it would actually make a 
_safe_ multiple-workdirs feature possible.

ATM the problem is that you can change a ref that is checked out 
elsewhere, and if you are not a Git expert, it will just make your life 
miserable.

However, if we do not pretend to have different repositories, but actually 
use the _identical_ repository for multiple working directories, we can 
make the mechanisms safe!

This is basically the reason why I do not like the current new-workdir 
script (and the patch in my private tree where I taught git-branch about 
it).

So while your approach may seem easier in the short run, there is no way 
you can make it safe.  No way, except going the full nine yards, and 
actually use the same repository, which means that you have to have the 
"other patches", too.

Ciao,
Dscho

--
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