Re: Consistent terminology: cached/staged/index
- From
Jon Seymour <jon.seymour@gmail.com>
- Date
- Feb 27, 2011, 22:28 UTC
- Message-ID
- <AANLkTinphmVJe8XW6BhjoyHgA38aopgEk=o=qEp4UT+4@mail.gmail.com>
- In-Reply-To
- <87bp1xest7.fsf@catnip.gol.com>
On Sun, Feb 27, 2011 at 8:21 PM, Miles Bader <miles@gnu.org> wrote:
Show 13 quoted lines
> Jeff King <peff@peff.net> writes: >> So the term "staging area" makes perfect sense to me; it is where we >> collect changes to make a commit. I am willing to accept that does not >> to others (native English speakers or no), and that we may need to come >> up with a better term. But I think just calling it "the stage" is even >> worse; it loses the concept that it is a place for collecting and >> organizing. > > Agreed. > > "Staging area" is a good noun (phrase) for this. "Stage" is a good verb > (for "move into the staging area"), but isn't intuitive as a noun. >
When used to describe a pre-production environment, the noun in my experience is inevitably 'staging' (short for staging environment) rather than 'stage' which is consistent with the origin Jeff posits.
I guess the noun 'stage' does have a use in git-speak to refer to the different arms of an unresolved merge.
jon.