git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Anjib Mulepati <anjibcs@hotmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Working directory managment
Date: Wed, 28 Mar 2012 11:39:39 -0400	[thread overview]
Message-ID: <BLU0-SMTP194A55718CFB9375EA9D7BBB14B0@phx.gbl> (raw)
In-Reply-To: <7v7gy4yd0w.fsf@alter.siamese.dyndns.org>

I am sorry if I haven't put my follow up question in proper place. It 
was on top. My question was

So these removed or replaced is done automatically or as I understood we 
do merge and and see conflict and do changes as per necessary?

i don't want to waste someone precious time but I am reading book and 
searching my own in internet to clear my confusion. That is not clear 
all time so that's why I am using this forum. I am reading all replies 
and trying to get basic concept as I go.

Thanks All
Anjib


On 3/28/2012 11:13 AM, Junio C Hamano wrote:
> Anjib Mulepati<anjibcs@hotmail.com>  writes:
>
>> What does it mean by this " Files in this directory are often removed
>> or replaced by Git as you switch branches"?
> Don't you already have an answer from me in the message you are responding
> to, which you quoted but perhaps you didn't read?
>
>
>

  reply	other threads:[~2012-03-28 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 16:12 Definition of working directory Anjib Mulepati
2012-03-27 17:10 ` Junio C Hamano
2012-03-27 21:26   ` Anjib Mulepati
2012-03-27 23:01     ` Junio C Hamano
2012-03-28  6:06     ` Kevin
2012-03-28  9:40     ` jaseem abid
2012-03-28 14:10   ` Working directory managment Anjib Mulepati
2012-03-28 15:13     ` Junio C Hamano
2012-03-28 15:39       ` Anjib Mulepati [this message]
2012-03-28 16:31         ` jaseem abid
2012-03-28 15:41     ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU0-SMTP194A55718CFB9375EA9D7BBB14B0@phx.gbl \
    --to=anjibcs@hotmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).