From: Jason Dunsmore <emacs-orgmode@dunsmor.com>
To: emacs-orgmode@gnu.org
Cc: Bernt Hansen <bernt@norang.ca>,
Carsten Dominik <carsten.dominik@gmail.com>,
Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: IMPORTANT: Migration of org-mode.git to the new server on sunday 5pm-7pm CET (UTC+1)
Date: Sat, 08 Jan 2011 20:46:58 -0600 [thread overview]
Message-ID: <87lj2ulrod.fsf@riotblast.dunsmor.com> (raw)
In-Reply-To: <DF68AE99-7085-4D4C-B18F-5162AE4D1A52@gmail.com> (Carsten Dominik's message of "Sat, 8 Jan 2011 11:04:35 +0100")
Carsten Dominik <carsten.dominik@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 <bernt@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.
next prev parent reply other threads:[~2011-01-09 2:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 22:12 IMPORTANT: Migration of org-mode.git to the new server on sunday 5pm-7pm CET (UTC+1) Bastien
2011-01-07 22:47 ` Bernt Hansen
2011-01-08 9:02 ` Bastien
2011-01-08 9:56 ` Carsten Dominik
2011-01-08 10:04 ` Carsten Dominik
2011-01-09 2:46 ` Jason Dunsmore [this message]
2011-01-09 13:52 ` Bastien
2011-01-08 9:07 ` Achim Gratz
2011-01-08 12:45 ` Bernt Hansen
2011-01-08 13:52 ` Achim Gratz
2011-01-09 14:01 ` Bastien
2011-01-09 14:23 ` Bastien
2011-01-09 16:05 ` Bastien
2011-01-09 17:46 ` Achim Gratz
2011-01-09 18:31 ` Bastien
2011-01-09 19:06 ` Jason Dunsmore
2011-01-09 19:36 ` Achim Gratz
2011-01-09 18:36 ` Konrad Hinsen
2011-01-09 18:46 ` Bastien
2011-01-09 19:10 ` Jambunathan K
2011-01-09 19:27 ` Jason Dunsmore
2011-01-09 19:19 ` Jason Dunsmore
2011-01-09 19:36 ` Bastien
2011-01-10 7:14 ` Konrad Hinsen
2011-01-10 0:44 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lj2ulrod.fsf@riotblast.dunsmor.com \
--to=emacs-orgmode@dunsmor.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).