From: Lars Vogel <lars.vogel@vogella.com>
To: git@vger.kernel.org
Subject: Usage of staging area instead of index still the way to go?
Date: Tue, 2 Feb 2016 11:30:12 +0100 [thread overview]
Message-ID: <CACA4a_Hmp-o2dDYRKd1tO0-nR5AebWOpgf5+VQ6vWV2Wcdd-NA@mail.gmail.com> (raw)
Hi,
I was about to send patches to the Eclipse Git project to replace the
usage of "Index" with "Staging area" based on this thread:
http://article.gmane.org/gmane.comp.version-control.git/233469/ which
Matthias Sohn (Project lead of EGit) send me a while ago.
But the Git help seem to use still heavily "index" instead of "staging
area". Is "staging area" still considered as the correct term or has
time proven that index is better?
Best regards,Lars
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@vogella.com, Web: http://www.vogella.com
reply other threads:[~2016-02-02 10:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACA4a_Hmp-o2dDYRKd1tO0-nR5AebWOpgf5+VQ6vWV2Wcdd-NA@mail.gmail.com \
--to=lars.vogel@vogella.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).