User: Password:
|
|
Subscribe / Log in / New account

DVCS-autosync

DVCS-autosync

Posted May 13, 2011 23:21 UTC (Fri) by martinfick (subscriber, #4455)
In reply to: DVCS-autosync by dlang
Parent article: DVCS-autosync

> switching your syncing from one branch to another would seem to be at least as problematic as re-generating your master branch.

I don't know how DVCS-autosync uses git, but there is nothing magical about "master" in git, in fact I rarely even care about it. All branches are equal with git, and all repos are equal. There is no need to even clone repos, simply init a new repo and fetch into it the branch you care about. git is a DVCS, it is not subversion.

> in addition, the history you want to keep around is usually the more recent stuff, rebasing the latest version onto old history seems to be loosing the most valuable revisions.

I fail to see how that is an argument against keeping history when the alternative, no history, surely is no better than the wrong history, is it?

But, who said anything about specifically cleaning up old history, clean up any history you want. Go ahead, clean it up to only one checkin, only the latest if you want. You will still be no worse off than having only one copy and you will have the ability to add history whenever you want.


(Log in to post comments)

DVCS-autosync

Posted May 14, 2011 9:21 UTC (Sat) by rmayr (subscriber, #16880) [Link]

> I don't know how DVCS-autosync uses git, but there is nothing magical about "master" in git, in fact I rarely even care about it. All branches are equal with git, and all repos are equal. There is no need to even clone repos, simply init a new repo and fetch into it the branch you care about. git is a DVCS, it is not subversion.

dvcs-autosync doesn't care about it at all. Whatever the checked out branch is, it will work on. Dieter and I have already been discussing that explicit support for branches may be good to have in future versions for accessing (and possibly modifying) older revisions. But right now, it's completely transparent. You can even have two clones of the repository (in different directories) pointing to different branches and have two instances of dvcs-autosync working on those branches concurrently.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds