From: Jorge Alberto Garcia <jorge.garcia.gonzalez@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Branches in Emacs Git repo
Date: Fri, 18 Mar 2016 12:00:54 -0600 [thread overview]
Message-ID: <CAPfrtUeELTcPdSQ5-+vtGfBttN+6UZvmaQDz8=ObTkU6d_nm2w@mail.gmail.com> (raw)
In-Reply-To: <87oaabg0nc.fsf@mbork.pl>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Fri, Mar 18, 2016 at 11:24 AM, Marcin Borkowski <mbork@mbork.pl> wrote:
> Hi,
>
> 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?
>
>
I think right now almost all new features and bug fixed are using branch
emacs-25, AFAIK once emacs-25 is considered stable enough it is merged
with
master branch.
> Is there any document explaining this things? If not, I'd be happy to
> write one (once I know that myself).
>
> Best,
>
some time ago Nicolas Petton send a url for a new website for emacs
may be he added some info about this. Meanwhile I suggest you to take a
look
at the mailing list archive to see how it went for others.
http://nicolas-petton.fr/ressources/emacs-website/
I myself struggled with this same situation where there is not an easy
intro for
new developers.
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Faculty of Mathematics and Computer Science
> Adam Mickiewicz University
>
>
[-- Attachment #2: Type: text/html, Size: 2434 bytes --]
next prev parent reply other threads:[~2016-03-18 18:00 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 [this message]
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
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
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='CAPfrtUeELTcPdSQ5-+vtGfBttN+6UZvmaQDz8=ObTkU6d_nm2w@mail.gmail.com' \
--to=jorge.garcia.gonzalez@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 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).