unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: casual contributing with git
Date: Sat, 18 May 2019 22:08:43 -0400	[thread overview]
Message-ID: <87v9y72o2c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <B58E31B7-D0AC-428E-A84C-D6158E27EE99@gmail.com>

The CONTRIBUTE [0] file in the Emacs repository should contain the
information you need with regards to the logistics of using git like
branching and the like.

[0]: https://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE

In short, usually you would develop on a local branch created from
latest master.  When you’re done and/or when you’d like to show your
work to others and get feedback, you create a patch from your changes,
e.g. using git-format-patch, and use your mail client to send it to the
correct mailing list for the project.  In the case of Emacs, that would
be one of emacs-devel@gnu.org (this list) or bug-gnu-emacs@gnu.org,
depending on the nature of your patch and e.g. if you’re fixing an
existing bug.  I skimmed through the first link in your email, and it
does mention format-patch at some point.

On a side note, instead of creating a patch with git-format-patch and
then sending it separately, you could also use git-send-email to create
a patch and send it at once.  There’s a nice interactive tutorial for
git-send-email over at https://git-send-email.io that walks you through
setting up and using git-send-email to create and send patches to a
project mailing list.

Hope this helps.



  reply	other threads:[~2019-05-19  2:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19  1:41 casual contributing with git Jean-Christophe Helary
2019-05-19  2:08 ` Amin Bandali [this message]
2019-05-19  2:30   ` Jean-Christophe Helary
2019-05-20  4:23     ` Amin Bandali
2019-05-19  4:48 ` Marcin Borkowski
2019-05-22  5:31   ` Eli Zaretskii
2019-05-24 17:05     ` Marcin Borkowski

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=87v9y72o2c.fsf@fencepost.gnu.org \
    --to=bandali@gnu.org \
    --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).