On Tue, Mar 1, 2011 at 6:46 PM, Drew Northup <drew.northup@xxxxxxxxx> wrote: > > On Tue, 2011-03-01 at 10:27 +0100, Alexey Feldgendler wrote: >> On Tue, 01 Mar 2011 10:11:11 +0100, David <bouncingcats@xxxxxxxxx> wrote: >> >> > A suggestion: could your conceptual bucket be named as "the precommit". >> > >> > Motives for this suggestion are: >> > 1) ÂI imagine this word will be readily translatable; >> >> Less so than âstaging areaâ, at least into Russian. >> >> Just my two cents. > > I was starting to think about "commit preparation area" this morning, > but it sounds horribly long. Would "Prep area" work provided that the > longer version has already been introduced into the discussion? This > provides a similar language metaphor to "staging area" hopefully without > the translation problem. > > Also, I still think that it is important to note somewhere that the way > that git handles commits is not the way that most users are likely to > imagine (the Index doesn't contain the blob objects itself; a finalized > commit is not just a bundled collection of everything as somebody might > expect; etc) so this "Prep area" is a logical space not completely > analogous to stuff found in the ".git" directory. Pretending that > complexity does not exist will not help; letting the users know that > they don't need to grok all of the details to get started is, on the > other hand, quite important. First I liked this proposal, but then I thought about 'git diff --preped' (doesn't really sound right). I think the term should: 1) Have a nice noun version; staging area, preparation area 2) Have a nice verb version; to stage, to prep 3) Have a nice past-participle; staged, cached Casting? Forging? I don't know, staging always seems right. Cheers. -- 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