Re: refactoring in GIT

From: Fredrik Gustafsson <iveqy@iveqy.com>
Date: Jun 28, 2011, 17:09 UTC
Message-ID: <20110628170926.GB910@paksenarrion.iveqy.com>
In-Reply-To: <loom.20110628T151105-908@post.gmane.org>

On Tue, Jun 28, 2011 at 01:19:23PM +0000, eugene wrote:

Show 20 quoted lines

> Hi,
>  I'm new to GIT and have two questions about code refactoring. 
> 
> #1. I want to refactor class A into few classes B,C,D. How should I check them 
> in and mark class A inactive so that development on A stops? Note, I do need A 
> stay in repository for backward compt. with prior code releases.
> 
> #2. [related question] What if another developer already had A in his local 
> repository, made changes and wants to commit after me. I just made A obsolete. 
> Does he have drop his changes and take B,C,D from me and/or merge?
> 
> Sorry if this question was already answered, pls point me.
> 
> Thanks,
> Eugene
> 
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

The only way I can imagine that you do that is by using submodules together with a repository permission management tool lite gitolite. Or Maybe just using gitolite with different branches. If I recall correctly gitolite has per branch rw permissions.

However, I doubt that this issue should be solved technically.

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com