From: Xue Fuqiao <xfq.free@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Branches in Emacs Git repo
Date: Sat, 19 Mar 2016 08:04:08 +0800 [thread overview]
Message-ID: <CAAF+z6HkQNYcCu7Un_L9HMEgMKnb8p4zzn2ZyfVVdZhwC8dcWg@mail.gmail.com> (raw)
In-Reply-To: <87oaabg0nc.fsf@mbork.pl>
On Sat, Mar 19, 2016 at 1:24 AM, Marcin Borkowski <mbork@mbork.pl> wrote:
> Hi,
Hi Marcin,
> since I'm planning to start contributing to Emacs, and I don't want to
> break something, I'd like to learn which branches are exactly for what
> and what should I do (assuming I will get write access at some point) -
> for instance, should I create small branches for my patches? Should
> they be branched from master?
>
> Is there any document explaining this things? If not, I'd be happy to
> write one (once I know that myself).
See CONTRIBUTE:
http://git.savannah.gnu.org/cgit/emacs.git/plain/CONTRIBUTE
For the release process and info about branches in Emacs, see
admin/release-process:
http://git.savannah.gnu.org/cgit/emacs.git/plain/admin/release-process
For ELPA-related information, see
http://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/README
If the information in these documents are not clear, you're welcome to
give us suggestions.
Thanks for wanting to contribute, welcome, and do not hesitate to ask
any further question, we are here to help!
next prev parent reply other threads:[~2016-03-19 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:24 Branches in Emacs Git repo Marcin Borkowski
2016-03-18 18:00 ` Jorge Alberto Garcia
2016-03-19 2:22 ` John Wiegley
2016-03-18 18:40 ` Eli Zaretskii
2016-03-18 20:01 ` Michael Heerdegen
2016-03-19 0:04 ` Xue Fuqiao [this message]
2016-03-19 21:37 ` Phillip Lord
2016-03-19 22:47 ` Stefan Monnier
2016-03-20 20:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAF+z6HkQNYcCu7Un_L9HMEgMKnb8p4zzn2ZyfVVdZhwC8dcWg@mail.gmail.com \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
/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.