Cool, I think I'll use something like this. (Except that I'll do `merge
--squash` to merge back my changes.)
Thanks Dale and Gergely!
On Mon, Mar 25, 2013 at 5:24 PM, Dale R. Worley wor...@alum.mit.edu wrote:
One approach might be to keep one set of branches that have your IDE
files, and one
One approach might be to keep one set of branches that have your IDE
files, and one set of branches that don't. Something like:
1. remote tracking branch from the authoritative repository
2. your working branch, without IDE files
3. your working branch(es), with IDE files
You work in #3.
That depends on your IDE. E.g. Netbeans cat store the project (IDE) files
in a separate directory, and as I remember, Eclipse can do the same.
On 22 March 2013 23:22, Ram Rachum ram.rac...@gmail.com wrote:
Hi everybody,
Here's a problem I had to deal with many times. I'm hoping someone here
Gergerly, that doesn't solve my problem. I want the files to be saved for
me to be able to use them on any computer in which I work on the repo.
On Sat, Mar 23, 2013 at 12:39 AM, Gergely Polonkai gerg...@polonkai.euwrote:
That depends on your IDE. E.g. Netbeans cat store the project (IDE)
If you manage to store them in a different directory, it will be easy to
manage them in a your own repository. E.g you check out the project source
in /home/user/project/source from git.project.com and the IDE files to
/home/user/project/ide from git.example.com, and combine them by using the
And this will be more convenient than a submodule?
On Sat, Mar 23, 2013 at 1:24 AM, Gergely Polonkai gerg...@polonkai.euwrote:
If you manage to store them in a different directory, it will be easy to
manage them in a your own repository. E.g you check out the project source
in
Submodules are committed with the project, so your fellow developers would
see that they exist. Also, submodules need to be committed separately,
while the approach I described can be automated with software like
SparkleShare (if you don't mind that you don't control the commit messages)
On 23
If the open-source project's repository is a submodule of my own, wouldn't
that work?
On Sat, Mar 23, 2013 at 1:32 AM, Gergely Polonkai gerg...@polonkai.euwrote:
Submodules are committed with the project, so your fellow developers would
see that they exist. Also, submodules need to be
