Carsten Dominik <carsten.domi...@gmail.com> writes: > On Jan 8, 2011, at 10:56 AM, Carsten Dominik wrote: > >> >> On Jan 8, 2011, at 10:02 AM, Bastien wrote: >> >>> Hi Bernt, >>> >>> Bernt Hansen <be...@norang.ca> writes: >>> >>>> Is it really necessary to rebuild the org-mode git repository (with >>>> filter-branch) to remove the ORGWEBPAGES/ content. Anyone with a >>>> clone >>>> and local branches of the existing repository will need to move >>>> all of >>>> these to the new repository. >>>> >>>> Would creating a commit to remove the ORGWEBPAGES directory in the >>>> existing repository not work just as well? This will keep all of >>>> the >>>> existing SHA1s for historical commits intact. >>> >>> I think you're right. Our goal was to remove ORGWEBPAGES/ into a new >>> repo with a proper history of its own. As Jason did that with >>> success, >>> I asked him to do the filtering for org-mode.git too -- which might >>> be >>> too much (my bad). >>> >>> Jason, Carsten, what is your take on this? >> >> I agree with Bernt. > > Sorry, let me be more specific. > > I am for moving the website to a separate repository. THis makes a > lot of sense. It does require to the release process though, because > my setup also used to update the webpage automatically. > > But I think that Bernt is right that it would be much better for users > if the git repo remains in tact, so that moving simple means changing > the pointer to the repo, and that local branches will survive. So > simple removing the webpage from the repo with a commit sounds like a > good idea to me. > > I don't think moving the webpage into a special branch is the right > solution.
I agree with Carsten and Bernt - keep the org-mode repo's history intact, remove ORGWEBPAGE in a commit, and split off ORGWEBPAGE into its own repo. _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
