From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: casual contributing with git Date: Sun, 19 May 2019 11:30:59 +0900 Message-ID: <6A7A458B-98F7-4852-8BA1-037BF7343633@gmail.com> References: <87v9y72o2c.fsf@fencepost.gnu.org> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_AFA59071-B766-49F5-94A9-9D03F4267FEB" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="261000"; mail-complaints-to="usenet@blaine.gmane.org" To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 19 04:31:20 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSBbb-0015lL-LL for ged-emacs-devel@m.gmane.org; Sun, 19 May 2019 04:31:19 +0200 Original-Received: from localhost ([127.0.0.1]:42552 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSBba-0004zZ-Ay for ged-emacs-devel@m.gmane.org; Sat, 18 May 2019 22:31:18 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:59040) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hSBbO-0004xG-Cj for emacs-devel@gnu.org; Sat, 18 May 2019 22:31:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hSBbM-00051g-UF for emacs-devel@gnu.org; Sat, 18 May 2019 22:31:06 -0400 Original-Received: from mail-pf1-x442.google.com ([2607:f8b0:4864:20::442]:35044) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hSBbM-00051G-L3 for emacs-devel@gnu.org; Sat, 18 May 2019 22:31:04 -0400 Original-Received: by mail-pf1-x442.google.com with SMTP id t87so5527450pfa.2 for ; Sat, 18 May 2019 19:31:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=ZDL3F6vrUnfLVYDpHmsheUvpvaFCJmJFYwS88IEj4SA=; b=MJrUVUJkXnPN64EwQt+Bzd3lSlh0QlYRGDvXuMtiavuVQTP7mo/LbUWOIXTtUhhhG0 Jy/3kflVetNYbCwOJRfJ6t5tkETdjkdGzYW6og0v6ETOpIFXhT7laB0hBH9IaFaXMi6j cpPle8ChZPTBzC3rrCMIVe9GmgIFa8gJhz+gCOrTESEKfvvhpFM1XqJupkO86/41v08g KQuOpT3/LYUWkO83+LhZ19QWkkekTSLPD3WR4yy4776XakkBr7AGDFrcElJsEWgvGYgI jSc3JjEyCZ7LjAwDpkOkEBNTlV9Az2F4GJmgtVYYI7mWHmwbqgodWT2wkU1PgNE+LHyY nX0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=ZDL3F6vrUnfLVYDpHmsheUvpvaFCJmJFYwS88IEj4SA=; b=En6FOPHuBvdfZLbpB/VF4jStDaMcSQdzvW7Oq5swQZHRjZ4EyKQEYxBS93G4c6SX4t HqljVQqlf0HzSf0Y3Zsrir1vzwPO1otB9Vy1C1n4Biyzf9z6TxSvUVvFPNq9jbULoo88 XW5rKHHFbQlcV+tXbRLOMR3cDVTWYgp2YRLqff7XGA4gkZTYUSRICAUB1jJEKXS6GTBm U0dtm3poRlCnyDBMd3G+1OpNKUqst4b9xWIBkrQEptvClBuaMccHksrXPygL0jPf+We5 CATg4P158TyzEryc2lcjYuXdQElt0loIQqqCPQ2nawTd02WC/YxGjUaPjiuquZ8ia4UY hcVw== X-Gm-Message-State: APjAAAXmeHoD8XjdADKFJqWmXjc+wizCBQYUvGnjWJV+AsOw2hBgftyU ZWrpG7LDf1TlNyl+L9qfQDJM/MOs X-Google-Smtp-Source: APXvYqyjRXG8B3cXYi9rkgSSlQqJkyFf0SeUkLHo6Zc87/tBjvCRNLJtQAfN82Vytt0qUsgh0gXQ7Q== X-Received: by 2002:a63:1119:: with SMTP id g25mr31537542pgl.380.1558233063065; Sat, 18 May 2019 19:31:03 -0700 (PDT) Original-Received: from [192.168.1.3] (pl32040.ag0304.nttpc.ne.jp. [111.89.228.40]) by smtp.gmail.com with ESMTPSA id n35sm18538861pgl.44.2019.05.18.19.31.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 May 2019 19:31:02 -0700 (PDT) In-Reply-To: <87v9y72o2c.fsf@fencepost.gnu.org> X-Mailer: Apple Mail (2.3445.104.8) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::442 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236740 Archived-At: --Apple-Mail=_AFA59071-B766-49F5-94A9-9D03F4267FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Thank you very much Amin. > On May 19, 2019, at 11:08, Amin Bandali wrote: >=20 > 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. >=20 > [0]: https://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE There is a discovery issue here because when you go to Savannah = (https://savannah.gnu.org/projects/emacs/) you don't find that kind of = information and instead find a link to EmacsWiki. What is the best way to propose changes to the Savannah top page ? Also, the Savannah page links to https://www.gnu.org/software/emacs/ = which is beautifully designed but has no information about = "contributing" or "developing" even in "Further information". What is the best way to propose changes to the gnu/emacs page ? > In short, usually you would develop on a local branch created from > latest master. When you=E2=80=99re done and/or when you=E2=80=99d = 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=E2=80=99re = fixing an > existing bug. I skimmed through the first link in your email, and it > does mention format-patch at some point. That's what I found out eventually. But the EmacsWiki pages don't really = address people who don't have write access so I was a bit confused. > 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=E2=80=99s 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. Thank you. > Hope this helps. Very much. Thank you again. Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune --Apple-Mail=_AFA59071-B766-49F5-94A9-9D03F4267FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Thank= you very much Amin.

On May 19, 2019, at 11:08, Amin = Bandali <bandali@gnu.org> wrote:

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=

There is a discovery issue here because when you = go to Savannah (https://savannah.gnu.org/projects/emacs/) you don't find = that kind of information and instead find a link to = EmacsWiki.

What is the best way to = propose changes to the Savannah top page ?

Also, the Savannah page links to https://www.gnu.org/software/emacs/ which is beautifully = designed but has no information about "contributing" or "developing" = even in "Further information".

What = is the best way to propose changes to the gnu/emacs page ?

In short, usually you would develop on a local branch = created from
latest master.  When you=E2=80=99re done = and/or when you=E2=80=99d 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=E2=80=99re fixing an
existing bug.  I skimmed through the first link in your = email, and it
does mention format-patch at some point.

That's = what I found out eventually. But the EmacsWiki pages don't really = address people who don't have write access so I was a bit = confused.

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=E2=80=99s 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.

Thank = you.

Hope this helps.

Very = much. Thank you again.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune


= --Apple-Mail=_AFA59071-B766-49F5-94A9-9D03F4267FEB--