From: Jorgen Schaefer <forcer@forcix.cx>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: johnw@gnu.org, Fabian Ezequiel Gallina <galli.87@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Replacing the `elpa' branch
Date: Sun, 10 Mar 2013 11:19:01 +0100 [thread overview]
Message-ID: <20130310111901.341789a5@forcix.kollektiv-hamburg.de> (raw)
In-Reply-To: <m2fw03znjv.fsf@igel.home>
On Sun, 10 Mar 2013 09:06:28 +0100
Andreas Schwab <schwab@linux-m68k.org> wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > I think the first step now is to figure out how to do step 2.
>
> git push git.sv.gnu.org:emacs/elpa will do it.
The problem we have faced I think was that elpa includes a number of
other projects as subtrees (using read-tree). The question was mostly
how to transport this information, in particular the "remote" branches,
to the git repository, as .git/config isn't chared. Alternatively, we
can use submodules for this. I'm not deep enough into git to understand
whether one or the other is "better" here.
Especially considering the one package using svn. I never used git-svn
for anything but trivial tasks, so I again have no idea how to include
that without a separate git repository that only tracks the svn one.
Regards,
-- Jorgen
next prev parent reply other threads:[~2013-03-10 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 20:33 Replacing the `elpa' branch Stefan Monnier
2013-02-16 14:06 ` Richard Stallman
2013-02-16 14:31 ` Stefan Monnier
2013-02-18 6:33 ` Leo Liu
2013-02-25 16:32 ` Ted Zlatanov
2013-03-09 5:02 ` Fabian Ezequiel Gallina
2013-03-10 5:18 ` Stefan Monnier
2013-03-10 8:06 ` Andreas Schwab
2013-03-10 10:19 ` Jorgen Schaefer [this message]
2013-03-10 11:57 ` Andreas Schwab
2013-03-10 12:06 ` Jorgen Schaefer
2013-03-10 16:35 ` Andreas Schwab
2013-03-10 12:44 ` Achim Gratz
2013-03-10 16:51 ` Jorgen Schaefer
2013-03-10 17:37 ` Dmitry Gutov
2013-03-10 17:41 ` Jorgen Schaefer
2013-03-10 18:52 ` Andreas Schwab
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130310111901.341789a5@forcix.kollektiv-hamburg.de \
--to=forcer@forcix.cx \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
--cc=johnw@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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.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).