Re: What is in git.git
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jan 21, 2006, 22:22 UTC
- Message-ID
- <7vu0bxjk5j.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <7vek31mkyg.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 13 quoted lines
> Alexander Litvinov <lan@ac-sw.com> writes: >... >> subpro and main are separate projects and master is the join >> of them. If I want to modify subpro I have to checkout subpro >> branch, edit files. When I have to got to master and bind new >> version of subpro to it. > > I do not see any problem with this.... >... >> Worse, if I will edit subpro's files bined to master branch >> changes will go to master branch instead of subpro's history. > > Simply untrue.
Sorry, these came out somewhat in a wrong way, so let me clarify.
What I meant was that there isn't anything coded so far that makes your worries real issues yet, and I do not intend to code Porcelainish scripts that are broken in the ways you see as problems in your message.
The point you raised are valid concerns. You need to keep them in mind when you start writing subproject aware version of git-checkout, git-commit and git-merge commands (among other things I might have forgotten, but I think these three covers pretty much everything). You are welcome to beat me to it, since I am not planning to do them right away.