public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ronald Ramos <ronjoe223@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [PATCH setup] Update README
Date: Sun, 31 Jul 2016 11:48:00 -0000	[thread overview]
Message-ID: <d6669ac9-edae-a4ab-2358-c45f8e9324c9@gmail.com> (raw)

commit 3863a3650acc481e62ee34bcc2bd836c301baaaf
Author: Ronald Ramos <ronjoe223@gmail.com>
Date:   Sun Jul 31 07:14:42 2016 -0400

     * README: Included git download URI. Also updated patch-submission 
instructions to refer to online manual.

diff --git a/README b/README
index 2582c05..c394e02 100644
--- a/README
+++ b/README
@@ -28,6 +28,10 @@ to make changes to the build system.

  Build commands:

+0) If building from git, obtain this project's code:
+   $ git clone git://sourceware.org/git/cygwin-apps/setup.git
+   $ cd setup
+
  1) Configure using this option
     $ /path/to/setup/bootstrap.sh
     This will automatically rebuild configure files and run configure
@@ -59,12 +63,14 @@ as a guide.

  SUBMITTING A PATCH:
  -------------------
-As per cygwin1.dll and many GNU projects:
+Follow the general directions given in the Cygwin contributions document:
+
+   https://cygwin.com/contrib.html
+
+The appropriate mailing list for this project is cygwin-apps
+(rather than cygwin-patches). Thus, the appropriate final command would be:

-No changelog in the patch itself.
-Attach the changelog to the email.
-Use, at a minimum "diff -uN" when constructing diffs for submission.
-As much as possible please provide only one goal per patch.
+   $ git send-email --to="cygwin-patches@cygwin.com"


  WISHLIST:

             reply	other threads:[~2016-07-31 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-31 11:48 Ronald Ramos [this message]
2016-08-01  8:07 ` Corinna Vinschen

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=d6669ac9-edae-a4ab-2358-c45f8e9324c9@gmail.com \
    --to=ronjoe223@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).