From: Bernt Hansen <bernt@norang.ca>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: Bastien Guerry <bzg@altern.org>,
Carsten Dominik <carsten@orgmode.org>,
emacs-orgmode@gnu.org
Subject: Re: IMPORTANT: Migration of org-mode.git to the new server on sunday 5pm-7pm CET (UTC+1)
Date: Sat, 08 Jan 2011 07:45:05 -0500 [thread overview]
Message-ID: <877heftvhq.fsf@norang.ca> (raw)
In-Reply-To: <87oc7rrcfs.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 08 Jan 2011 10:07:19 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Hi Bastien,
>
> Bastien <bastien.guerry@wikimedia.fr> writes:
>> It will be important to clone again after the migration as this repo
>> comes with a major change: there is no ORGWEBPAGES/ directory anymore.
>> We have moved ORGWEBPAGES/ in a separate repo, which might get public
>> later.
>
> As Bernt Hansen has already remarked, this is somewhat against the
> spirit of Git... There may be reasons to do what you seem to want to
> do, but I don't get what they might be at the moment - could you
> perhaps elaborate?
>
> May I ask you to consider to just put ORGWEBPAGES into a separate
> branch? More specifically, create a new branch for ORGWEBPAGES and rm
> all other stuff, then rm ORGWEBPAGES from the master / maint branches.
> This way it's easy enough to build clones that track all or just
> selected branches from a single repository which preserves commit
> history.
It's perfectly okay to extract the ORGWEBPAGE content and history into
a new repository for future work on the website. We can then remove the
ORGWEBPAGES directory with a single commit in the org-mode.git
repository since that is no longer being used and move forward from
there.
There's no reason to keep the ORGWEBPAGE directory around in a branch in
org-mode.git repository if it isn't ever going to be used again. I
think deleting the content with a commit is the correct way to deal with
this in org-mode.git.
The only reason to use filter-branch to remove the ORGWEBPAGE history
and content (and create a totally new repository with new SHA1 for every
historical commit) is if it contained some proprietary stuff that really
should not be shared with the public. You would do this before making
the repository public and for org-mode.git it is already way to late for
that.
Using filter-branch on an existing git repository is highly intrusive
since it breaks everyone's clone of the repository and any work in
process needs to be extracted and applied to the new repository. It's
doable but painful and something that we should strive to avoid unless
it is absolutely necessary.
HTH,
Bernt
next prev parent reply other threads:[~2011-01-08 12:45 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
2011-01-09 13:52 ` Bastien
2011-01-08 9:07 ` Achim Gratz
2011-01-08 12:45 ` Bernt Hansen [this message]
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=877heftvhq.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=Stromeko@nexgo.de \
--cc=bzg@altern.org \
--cc=carsten@orgmode.org \
--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).