Dylan Kinnett <dy...@nocategories.net> writes:
> Would it be better, then, to create a fork, instead of a branch? (I don't
> understand forks just yet.) In my situation here, I wouldn't want to treat
> the non-edited files as deleted although I would want to move the changes
> back to the master version, but also I also wouldn't want the sub-set to
> contain all of the files.
I'm not sure what you meant by "a fork", but if you meant a clone of
your original repository, then for git this is only another branch, that
is in another git repository. Nothing special.
To solve this, I would probably create, in a special branch, a sub
directory where I would move the sub-set. Then I would edit the file
there, and move back the sub-set in the main directory once I'm done.
vcs-home mailing list