Karsten Blees wrote: > Am 15.10.2013 00:29, schrieb Felipe Contreras: > > tl;dr: everyone except Junio C Hamano and Drew Northup agrees; we should move > > away from the name "the index". > > > > It has been discussed many times in the past that 'index' is not an > > appropriate description for what the high-level user does with it, and > > it has been agreed that 'staging area' is the best term. > > I haven't followed the previous discussion, but if a final conclusion towards > 'staging area' has already been reached, it should probably be revised. > > > The term 'staging area' is more intuitive for newcomers which are more > > familiar with English than with Git, and it seems to be a > > straightforward mental notion for people with different mother tongues. > > > > In fact it is so intuitive that it's used already in a lot online > > documentation, and the people that do teach Git professionally use this > > term, because it's easier for many kinds of audiences to grasp. > > Such online documentation often portraits the 'staging area' as some > supposedly 'unique' git feature, which I find _very_ confusing. In fact, > every major SCM has a staging area. E.g. you first need to "svn/hg/bzr/p4 > add/remove/rename/move" a file, which is somehow recorded in the working > copy. These recorded changes will then be picked up by a subsequent > "svn/hg/bzr/p4 commit/submit". That is not a staging area. % hg init test % cd test % echo Hello > README % hg add README % echo Bye > README % hg commit -m Init % hg log -p -r -1 changeset: 0:ba28df72474c tag: tip user: Felipe Contreras <felipe.contreras@xxxxxxxxx> date: Fri Oct 18 19:43:42 2013 -0500 summary: Init diff -r 000000000000 -r ba28df72474c README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Fri Oct 18 19:43:42 2013 -0500 @@ -0,0 +1,1 @@ +Bye What exactly got staged? To me the best way to think about the staging area is like a commit draft. No other VCS has anything like that. And what is the point about this argument? > > index: an 'index' is a guide of pointers to something else; a book > > index has a list of entries so the reader can locate information > > easily without having to go through the whole book. Git porcelain is > > not using the staging area to find out entries quicker; it's not an > > index. > > The 'staging area' is a sorted list of most recently checked out files, and > its primary purpose is to quickly detect changes in the working copy (i.e. > its an index). That is not it's primary purpose. > Of the 28 builtin main porcelain commands, 18 read the index (read_index), > and 11 of those also check the state of the working copy (ie_match_stat). > Incidentally, the latter include _all_ commands that update the so-called > 'staging area'. > > Subversion until recently kept the checked out files scattered in > **/.svn/text-base directories, and many operations were terribly slow due to > this. Subversion 1.7 introduced a new working copy format, based on a > database in the root .svn directory (i.e. an index), leading to tremendous > performance improvements. > > The git index is a major feature that facilitates the incredible performance > we're so much addicted to...why be shy about it and call it something else? Tell me which subversion command adds and removes information from their working copy metadata, which is not a used as a staging area, commit draft, or even an index. Moreover, we are not discussing about Git's index file, that low level concept will stay the same, we are talking about the high level concept. > > stage: a 'stage' is a special area designated for convenience in order > > for some activity to take place; an orator would prepare a stage in > > order for her speak to be successful, otherwise many people might not > > be able to hear, or see her. Git porcelain is using the staging area > > precisely as a special area to be separated from the working directory > > for convenience. > > I'm not a native speaker, but in my limited understanding, 'staging' in > computer jargon is the process of preparing data for a production system > (i.e. until the 'stage' or 'state' of the data is ready for production). It > has nothing to do with the 'stage' in a theater. It is the same. A stage in the theater is also used for preparing a production. > I've never heard the term 'staging' beeing used for source code or software > (that would be 'integration'). I've also never heard 'staging' for moving > data back from a production system to some work- or development area. Then why are people using it in external documentation? Why is ProGit already using it? But more importantly: do you have a better name? > In any sense, 'staging' is a unidirectional process (even in a theater). It is not. Props and utilites are added and removed from the stage. > If I think of the index as a staging area, it covers just a single use case: > preparing new commits. That is its main purpose. > With this world view, it is completely counter-intuitive that e.g. changing > branches overwrites my staging area. Why would it do that? It's preparing the next commit, on top of which branch is not defined yet. > IMO, it is ok to use 'like a staging area' when we talk about using the index > to prepare new commits. Which is how it is being proposed; changing the name of the high-level concept. > However, its not ok to use 'staging area' as a general synonym for the index. Nobody is proposing that; the low-level "index file" stays the same. -- Felipe Contreras -- 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