git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Changsheng Jiang <jiangzuoyan@gmail.com>
To: "Rob (gmail)" <robvanb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: New to Git / Questions about single user / multiple projects
Date: Wed, 19 Aug 2009 10:24:46 +0800	[thread overview]
Message-ID: <eafc0afe0908181924x60e5dd23vd37711db880ead84@mail.gmail.com> (raw)
In-Reply-To: <a2db4dd50908181852s1e2c64fen8b883faf76b3136d@mail.gmail.com>

I am not that familiar with git too, but see the answers below
questions, respectively, and fix me if i am wrong.

On Wed, Aug 19, 2009 at 09:52, Rob (gmail) <robvanb@gmail.com> wrote:
>
> I'm new to git and have some (I think) basic questions that I have not
> been able to find answers to in the documentation.
> It's very possible that these are the result of my lack in
> understanding git / version control, so feel free to point me to
> documentation
> that might contain the answers.
>
> I'm doing ERP development for my job and various 'hobby' development
> in my spare time.
> I'd like to track/store/ version control the code that I write for
> both work and play.
> I am (currently) working by myself, no need to have multiple
> developers working of the same code.
>
> Q1:
> Can I create a single repository (project?) for all my code, knowing
> that there are multiple small, unrelated projects. Or should I create
> a new repository for each project ?
git-submodule
>
> Q2:
> After initalizing my repository, and comitting the 1st batch of code:
> When further working on the code, will the command "git add ." add all
> changed and new files ? Or do I specifically need to list the new
> files ?
=git status= or =git ls-files= will list the files in different statuses.

If there are no other files, such as backup file produced by editor,
you can run =git add .=. If there are, try to configure in file
=.git/info/exclude= or =.gitignore=.

Changed files can be committed automatically by =git commit -a=
>
> Q3: Can I run 'git add x' in any subdirectory, or do I need to issue
> if from the root of the project ?
You can.
>
> Thanks,
>
> Rob.
>
> --
> When in trouble or in doubt, run in circles, scream and shout
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

                                                     Changsheng Jiang

  reply	other threads:[~2009-08-19  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  1:52 New to Git / Questions about single user / multiple projects Rob (gmail)
2009-08-19  2:24 ` Changsheng Jiang [this message]
2009-08-19  4:14   ` Chris Packham
2009-08-19  4:00 ` Daniel Barkalow
2009-08-19  7:59 ` Jakub Narebski
2009-08-19 11:00   ` Rob (gmail)
2009-08-19 12:18     ` Jakub Narebski
2009-08-19 12:28       ` Rob (gmail)
2009-08-19 12:49         ` Jeff King
2009-08-19 12:48       ` Jeff King
2009-08-19 13:20         ` Jakub Narebski

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=eafc0afe0908181924x60e5dd23vd37711db880ead84@mail.gmail.com \
    --to=jiangzuoyan@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=robvanb@gmail.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.
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).