On Mar 31, 6:03 pm, Rick DeNatale <rick.denat...@gmail.com> wrote:
> On Wed, Mar 31, 2010 at 12:11 PM, vfclists <vfcli...@googlemail.com> wrote:
> > On Mar 31, 4:20 pm, Rick DeNatale <rick.denat...@gmail.com> wrote:
> >> Is this what you are looking for?
> > Using .gitignore is something I have considered, but it looks like it
> > is going to get more interesting than that.
> > I will probably have to use separate directories, and use some kind of
> > condititional excludes or includes if .gitignore supports something
> > like that.
> > Does checking out a branch erase all the directories and files in the
> > working directory and replace them with only the contents of the
> > branch?
> Only files which are tracked will be affected by a checkout.
> Files don't get tracked until you git add them.
> .gitignore is a way to keep new files from being tracked.
Does this mean that if you checkout a branch, only files that you add
are committed, even if in the original branch they are still tracked?
That will be a new discovery for me if that is the way git works.
It will make things a lot easier for me it it works that way. I could
remove all the files and add only the ones I need to change.
> Rick DeNatale
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at