1

Topic: At me a problem with branches SCC

I write the program and I use to it, I write one. Sometimes happens so that leaving unfinished one feature it is necessary to undertake another. In the history  it would be desirable each feature to see in a separate branch. The problem what even the left unfinished feature is already useful also to me would be desirable it to use as is, and if I switch to a new branch of the second feature branched off from master I lose changes of a branch of the first feature (in sense in SCC a branch of the first feature remains, but in the operating code of changes of the first feature was not present, and it would be desirable to use). It would be possible  in the master the left unfinished features, and  branches to branch off in proper places, but somehow it does not look beautifully. It would be beautiful - the branch branched off, completely a feature described,  in the master. How further to live?

2

Re: At me a problem with branches SCC

3

Re: At me a problem with branches SCC

4

Re: At me a problem with branches SCC

Hello, Ejnstok Fajr, you wrote: > In the history  it would be desirable each feature to see in a separate branch. And if to divide source codes not on layers and on features so that to each feature there corresponded one folder. Then in VCS it will be possible to look history for separate folders-features. So ?

5

Re: At me a problem with branches SCC

CF> It is possible to branch off from the current left unfinished branch Admit I from master branched off branch A, from it branch B, from it a C branch. What commands git to me should be fulfilled, that  in the master only branch B? (Thus A the branch of a C from branch A should branch off from new peak in master, and.

6

Re: At me a problem with branches SCC