From: phillip.lord@russet.org.uk (Phillip Lord)
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: ELPA contributions?
Date: Tue, 13 Oct 2015 10:27:02 +0100 [thread overview]
Message-ID: <87d1wjt8yh.fsf@russet.org.uk> (raw)
In-Reply-To: <CAAdUY-J9U-Ax69WjJxjM4+xwhTg9oewgdD5BwfPkFFH0=M699A@mail.gmail.com> (Artur Malabarba's message of "Mon, 12 Oct 2015 22:54:57 +0100")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
>> I share the same feeling. The bit that scares me is pushing to ELPA.
>> Everything else is disposable. If I pull the wrong thing (like
>> elpa/master) to local, then I can just delete and start again. If I push
>> the wrong thing to phillord/dash.el that's more of a pain, but not a
>> disaster. But if I push my local master to the elpa master branch
>> (rather than externals) I do not know what will happen, but I suspect it
>> will be bad.
>
> This is git. It's pretty hard to mess up.
Git is many things but "pretty hard to mess up" is not one of them, in
my experience.
> In particular, you can't push anything that's not a fast forward unless you
> --force, and you usually can't --force push to master. Again, I'm not at
> the pc ATM, but I'm pretty sure that's the case for elpa.git. Hell,
> emacs.git won't even let me push if it doesn't like the commit message.
That's reassuring anyway, although I don't know a good way of testing it
(safely!).
Phil
next prev parent reply other threads:[~2015-10-13 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:32 ELPA contributions? David Kastrup
2015-10-09 22:42 ` Artur Malabarba
2015-10-10 6:55 ` David Kastrup
2015-10-10 7:00 ` David Kastrup
2015-10-10 22:24 ` Artur Malabarba
2015-10-10 22:26 ` Artur Malabarba
2015-10-12 12:44 ` Phillip Lord
2015-10-12 16:00 ` Eric Abrahamsen
2015-10-12 20:54 ` Phillip Lord
2015-10-12 21:54 ` Artur Malabarba
2015-10-13 9:27 ` Phillip Lord [this message]
2015-10-12 21:25 ` Artur Malabarba
2015-10-12 22:14 ` Eric Abrahamsen
2015-10-12 22:32 ` Eric Abrahamsen
2015-10-13 9:35 ` Phillip Lord
2015-10-13 11:30 ` Artur Malabarba
2015-10-13 17:38 ` Eric Abrahamsen
2015-10-14 11:14 ` Phillip Lord
2015-10-12 21:44 ` Artur Malabarba
2015-10-13 11:15 ` Phillip Lord
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=87d1wjt8yh.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).