From: jaseem abid <jaseemabid@gmail.com>
To: Anjib Mulepati <anjibcs@hotmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Definition of working directory
Date: Wed, 28 Mar 2012 15:10:52 +0530 [thread overview]
Message-ID: <CAH-tXsCG5c-z_P-Uw7h72847e0ThfFREFVKkqcG77LuF4fQoTA@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP4376CA011AD4D79C1BAB727B14A0@phx.gbl>
On Wed, Mar 28, 2012 at 2:56 AM, Anjib Mulepati <anjibcs@hotmail.com> wrote:
>
> So if I have a project called MyProject and inside that I have two
> sub-directories dir1 and dir2. Does that mean working directory is *ALWAYS*
> MyProject.
Yes. It is MyProject.
> Also if i create some file in dir1 and do git status without git add then
> it display untracked files as ../dir1/
> It doesn't display the untracked file name but after I do git add when I
> did git status it does give me file under changes to be committed. Why
> didn't it shows file with name as untracked in first case?
Often there will be build folders with too many unwanted files to
ignore. Unless at least a single file in a directory is tracked, git
will ignore the folder. This is afaik a good feature and not a
problem.
PS: I am not really a git expert. Please correct me if I'm wrong.
--
Jaseem Abid
+91 8891 72 43 72
S6 CSE student
National Institute of Technology , Calicut.
next prev parent reply other threads:[~2012-03-28 9:41 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 [this message]
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
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=CAH-tXsCG5c-z_P-Uw7h72847e0ThfFREFVKkqcG77LuF4fQoTA@mail.gmail.com \
--to=jaseemabid@gmail.com \
--cc=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).