Git development
 help / color / mirror / Atom feed
From: "J. Bakshi" <joydeep@infoservices.in>
To: Chris Packham <judge.packham@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: about directory management
Date: Tue, 19 Jul 2011 13:23:33 +0530	[thread overview]
Message-ID: <20110719132333.1713c52b@shiva.selfip.org> (raw)
In-Reply-To: <4E253603.7020403@gmail.com>

On Tue, 19 Jul 2011 19:45:07 +1200
Chris Packham <judge.packham@gmail.com> wrote:

> On 19/07/11 18:07, J. Bakshi wrote:
> > Hello,
> > 
> > I need to add directory structure in my git repo where some of the directory are empty but still need to add those to maintain the structure. I also need to add directory as non-recursive, so that I can add the final child directory so get the structure. How can git help to do these ?
> > 
> > Thanks
> > --
> 
> One of the things that makes git different from other SCMs is that it
> tracks sets of changes (i.e. commits) not individual files/directories.
> My initial response is to tell you to create the directories when you've
> got something to put into them and not before. If they are needed for
> compilation of your code then make it part of the build process. If you
> do have a reason for needing empty directories the standard response is
> to put a .dummy file in the directory (you only need it in the deepest
> directory, not every directory on the path).
> 
> 

Thanks for your valuable clarification and notes.

      reply	other threads:[~2011-07-19  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19  6:07 about directory management J. Bakshi
2011-07-19  7:45 ` Chris Packham
2011-07-19  7:53   ` J. Bakshi [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=20110719132333.1713c52b@shiva.selfip.org \
    --to=joydeep@infoservices.in \
    --cc=git@vger.kernel.org \
    --cc=judge.packham@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