Git development
 help / color / mirror / Atom feed
From: "Dennis" <denny@dennymagicsite.com>
To: <git@vger.kernel.org>
Subject: Looking for a way to set up Git correctly
Date: Wed, 10 Nov 2010 22:25:31 -0500	[thread overview]
Message-ID: <BD94CB4FDD0C4462804E316F814A3CCA@denny> (raw)

I have a situation.

I have started a web project (call it branch1), and have maintained it 
without a version control system for quite some time.
Then, I copied it to another folder (branch2) and while the project remained 
essentially the same, I have changed a few of internal paths and some 
variable names inside the files.
Then, a few months later on, I copied branch2 to a folder called branch3 and 
also modified some of the variable names and some of the internal structure 
of the files.

Thus I ended up with 3 folders on my local HDD with pretty much the same 
file names and folder structure and everything, and most of the file 
content, except those small deltas that made those files different for each 
branch.

I guess it's never too late, and now I want to put these 3 projects into a 
version control system, and I chose git.

Now, this can be either really simple or really complicated.  My first 
question is:  how do I set the repository up in the proper way where I could 
work on all 3 projects separately, with additional possibility of working on 
branch1 only and later committing my changes to branch2 and branch3.  (Since 
projects are virtually identical, a fix in one branch usually needs to be 
propagated to other branches)
First, I assume I will use a single repository for this.  Then, do I simply 
set up 3 branches and start using them, or is there a way to set git up to 
capitalize on the projects being nearly identical?

My second question is that each branch has a huge folder with image data. 
By huge I mean 1 to 4Gb, depending on the branch.  Since images are not 
directly relevant to the development work, is there a way to not include 
those folders in git?  To be honest though, I probably should include them, 
but I wanted to ask about this separately as git repository may be get 
large, since all 3 branches may grow to 9Gb or so.

Thus I am looking for a git way to handle my situation.  Is this simple or 
is is hard?
Are there any recommendations before I jump in?
Dennis 

             reply	other threads:[~2010-11-11  3:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  3:25 Dennis [this message]
2010-11-11  9:38 ` Looking for a way to set up Git correctly Alex Riesen
2010-11-11 13:25 ` Enrico Weigelt
2010-11-11 16:46   ` Jonathan Nieder
     [not found]     ` <20101111190724.00vcimqm8w0cw8s0@dennymagicsite.com>
2010-11-11 19:38       ` Jonathan Nieder

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=BD94CB4FDD0C4462804E316F814A3CCA@denny \
    --to=denny@dennymagicsite.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox