All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: anjibman <anjibcs@hotmail.com>
Cc: git@vger.kernel.org
Subject: Re: Index area concept and blowing it up
Date: Thu, 29 Mar 2012 12:42:56 +0200	[thread overview]
Message-ID: <4F743CB0.8050603@op5.se> (raw)
In-Reply-To: <1332987064083-7416124.post@n2.nabble.com>

On 03/29/2012 04:11 AM, anjibman wrote:
> Hi All,
> 
> My first question is where is this index actually in Git. Is that a some
> folder or some location?
> 
> Second, how really Git keep information about index?
> 
> Third, in git community book it says " If you blow the index away entirely,
> you generally haven't lost any information as long as you have the name of
> the tree that it described". I didn't get this statement can any one explain
> this in simple words.
> 
> And finally why git add is used for both adding untrack file as well as to
> move file to stage area? Is there any particular reason for this?
> 

index = staging area.
committing = creating a commit object out of the staging area.

When a book talks about "move file to staging area", it really means
"add to the set of files we're about to create a commit object from".

That might help clear things up. 

However; Your questions all seem rather technical, but you don't strike
me as a programmer yourself. If you give us the reason behind your
questions, it'll almost certainly be easier for us to answer them in a
way that's useful to you while wasting the minimum amount of our time.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

      reply	other threads:[~2012-03-29 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  2:11 Index area concept and blowing it up anjibman
2012-03-29 10:42 ` Andreas Ericsson [this message]

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=4F743CB0.8050603@op5.se \
    --to=ae@op5.se \
    --cc=anjibcs@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.