From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Bernt Hansen <bernt@norang.ca>, emacs-orgmode@gnu.org
Subject: Re: Re: IMPORTANT: Migration of org-mode.git to the new server on sunday 5pm-7pm CET (UTC+1)
Date: Sat, 8 Jan 2011 10:56:50 +0100 [thread overview]
Message-ID: <A7F1CBB6-3858-4389-91DA-21B4EA59A1FB@gmail.com> (raw)
In-Reply-To: <87pqs7ydic.fsf@gnu.org>
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.
Cheers
- Carsten
>
>> If you remove the ORGWEBPAGES directory with just a commit in the
>> org-mode repository then the SHA1's of previous commits will not
>> change
>
> Which is more in the spirit of what git allows: keep the revision
> history as *truthful* as possible.
>
>> and we can just change the URL to point at the new server and we're
>> done.
>
> I'm for the direction you suggest -- I let Jason and Carsten tell me
> what they think before deciding.
>
> Thanks for voicing this in time!
>
> --
> Bastien
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2011-01-08 9:56 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 [this message]
2011-01-08 10:04 ` Carsten Dominik
2011-01-09 2:46 ` Jason Dunsmore
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=A7F1CBB6-3858-4389-91DA-21B4EA59A1FB@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=bernt@norang.ca \
--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).