From: Jakub Narebski Date: Fri, 06 Oct 2006 10:56:48 GMT Subject: Re: Unresolved issues #4 Message-ID: In-Reply-To: <7vfye20xjt.fsf@assigned-by-dhcp.cox.net> Junio C Hamano wrote: > Recent issues I am aware of but haven't kept track of closely > enough and as a result do not have a clue about X-<. > > From: A Large Angry SCM > Subject: Notes on Using Git with Subprojects > Message-ID: <45196628.9010107@gmail.com> > > [jc: a very nice write-up of a subprojects workflow. I do not > remember if it produced any actionable items, though] It did produce two workflows: the original "build time" by A Large Angry SCM/Gitzilla, which I think is/will be available at http://git.rsbx.net/Notes/Git_Subprojects.txt and second using linked objects and refs. Both I think not quite finished; perhaps some of the code could be put in 'pu'. Perhaps to be added to Subpro.txt in 'todo' branch, and/or to git wiki... > From: Shawn Pearce > Message-ID: <20060930045037.GB18479@spearce.org> > > "git ref-log" command to interact with ref-log? > > [jc: not much interest from users?] I thing it can increase number of reflog users. > From: Josh Triplett > Message-ID: <451A30E4.50801@freedesktop.org> > > git-split Should be git-split-hierarchy or git-split-by-directory I think. We could have also git-split-history, which would split current history into archive repository, and active repository with archive repository grafted in; or add to archive repository if it exists, regraft active (current work) repository and prune below new grafts. > [jc: no response to the initial review comments] It is "done once" problem, and usable only for some repositories, so perhaps this is the cause of not many responses. -- Jakub Narebski Warsaw, Poland ShadeHawk on #git