From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: Branches in Emacs Git repo
Date: Fri, 18 Mar 2016 21:01:30 +0100 [thread overview]
Message-ID: <87bn6bimhx.fsf@web.de> (raw)
In-Reply-To: 87oaabg0nc.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
> 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?
Don't be too frightened. Any patch can introduce breakage if unexpected
things happen. It happens to regular contributers too. Of course you
should be careful, but don't thwart yourself, I think you are totally
able to rate your work.
If it helps, you can post a commit on emacs-devel before pushing for
review. I did that a while ago to be sure that I respected all commit
message rules.
Regards,
Michael.
next prev parent reply other threads:[~2016-03-18 20:01 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 [this message]
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=87bn6bimhx.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.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).