Junio C Hamano, 18.12.2008: > Markus Heidelberg <markus.heidelberg@xxxxxx> writes: > > > in the "Merging external work" section of the gitcore-tutorial it is > > stated that the rsync transport is deprecated. The description was added > > in commit 914328a (Update tutorial., 2005-08-30) together with the > > "deprecated" note. Having never heard/read this before and since this > > commit is quite old, I wonder if it is still the case or there was a > > solution for this problem. > > Sorry, I do not quite understand what you perceive as "this problem". The problem described in the rsync section in gitcore-tutorial: "can produce unexpected results when you download from the public repository while the repository owner is uploading into it via rsync transport. Most notably, it could update the files under refs/ which holds the object name of the topmost commits before uploading the files in objects/ - the downloader would obtain head commit object name while that object itself is still not available in the repository." I only thought about git itself uploading into and downloading from the repository with push and fetch, respectively. And wondered where the problem with the order of refs and objects was. But I just realized, it can of course be uploaded with plain rsync, too. > It has been deprecated for too long a time. Maybe it is time to remove > the support, instead of carrying the deprecated command forever? Is that > the problem you are talking about? Yes, this is the answer to my question. I thought maybe it's not deprecated anymore, because the only place where it is called so, is gitcore-tutorial. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
