From: Andreas Schwab <schwab@linux-m68k.org>
To: Jorgen Schaefer <forcer@forcix.cx>
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 12:57:17 +0100 [thread overview]
Message-ID: <m2boarzcv6.fsf@igel.home> (raw)
In-Reply-To: <20130310111901.341789a5@forcix.kollektiv-hamburg.de> (Jorgen Schaefer's message of "Sun, 10 Mar 2013 11:19:01 +0100")
Jorgen Schaefer <forcer@forcix.cx> writes:
> 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,
You can push any branch, just name it in a refspec.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-03-10 11:57 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
2013-03-10 11:57 ` Andreas Schwab [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2boarzcv6.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=forcer@forcix.cx \
--cc=galli.87@gmail.com \
--cc=johnw@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.