I have no `man` at hand to check this, but as I remember, if you ignore
those files (put them in .gitignore or .git/info/exclude), git won't
complain about them.
However, if you have already added those files in an old commit, you will
have to remove them on each branch
On 8 Jan 2015 19:20, <rpa...@shipco.com> wrote:
> Dear All,
> In my current project, I have to work on multiple feature branches
> I generally creates feature branch from development branch, and I have to
> rebase feature branch with development branch.
> I am using eclipse for development.
> Now, the problem is when I do rebase, I want to ignore eclipse setting
> files(e.g. .project, .classpath etc.), but they don't. How to do that?
> And second issue is when I switch from one branch to another branch, it's
> asking me to stash/commit files, which I don't want. I want those files to
> be common for all branches, and I don't want to even commit those files.
> Those files are changed just for my development and testing purpose. So,
> what changes I have to do to avoid those files?
> Please suggest me.
> Ritesh Patel.
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.