From: Siva Chandra <sivachandra@google.com>
To: Joel Brobecker <brobecker@adacore.com>, Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] - Improve suggestions for generating patches in CONTRIBUTE
Date: Tue, 17 Apr 2012 07:26:00 -0000 [thread overview]
Message-ID: <CAGyQ6gzAv4g8OV+xzawJ6ETFrNJ5qndzwEi9i0KQ76Ha_8u7Ow@mail.gmail.com> (raw)
In-Reply-To: <4F8C34A8.30101@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Joel> Personally, I'd even get rid of the "diff -cp" alternative. We'll
Joel> continue accepting context diffs, but I think that suggesting it,
Joel> even if we say later on that we prefer unified diffs, will result
Joel> in more patches sent in that format.
Pedro> Completely agreed. /me pokes at Stan. :-)
Joel> If we do not want to remove
Joel> the context diff alternative, then at least let's put it second.
I have modified to put the context diff alternative second. I did not
remove it altogether as I have not seen more support to removing it.
2012-04-17 Siva Chandra Reddy <sivachandra@google.com>
* CONTRIBUTE: Add "cvs diff -up" as a way to generate patches
when accessing the CVS repository. Add a note saying that the
"-up" flavors of "cvs diff" and "diff" are preferred.
Thanks,
Siva Chandra
[-- Attachment #2: contribute_patch_v2.txt --]
[-- Type: text/plain, Size: 992 bytes --]
Index: CONTRIBUTE
===================================================================
RCS file: /cvs/src/src/gdb/CONTRIBUTE,v
retrieving revision 1.12
diff -u -p -r1.12 CONTRIBUTE
--- CONTRIBUTE 22 Aug 2009 17:08:09 -0000 1.12
+++ CONTRIBUTE 17 Apr 2012 06:52:34 -0000
@@ -71,9 +71,11 @@ o Submitting Patches
documentation (i.e., .texi files).
The patch itself. If you are accessing the CVS repository use
- "cvs update; cvs diff -cp"; else, use "diff -cp OLD NEW" or
- "diff -up OLD NEW". If your version of diff does not support
- these options, then get the latest version of GNU diff.
+ "cvs update; cvs diff -up" or "cvs update; cvs diff -cp"; else,
+ use "diff -up OLD NEW" or "diff -cp OLD NEW". The flavors with
+ "-up" option string are preferred. If your version of diff does
+ not support these options, then get the latest version of GNU
+ diff.
We accept patches as plain text (preferred for the compilers
themselves), MIME attachments (preferred for the web pages),
next prev parent reply other threads:[~2012-04-17 7:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 7:50 Siva Chandra
2012-04-16 14:56 ` Joel Brobecker
2012-04-16 15:07 ` Pedro Alves
2012-04-17 7:26 ` Siva Chandra [this message]
2012-04-17 15:11 ` Joel Brobecker
2012-04-17 15:48 ` Mark Kettenis
2012-04-24 7:10 ` Siva Chandra
2012-04-24 17:39 ` Eli Zaretskii
2012-04-24 20:24 ` Joel Brobecker
2012-04-25 5:47 ` Eli Zaretskii
2012-04-25 8:06 ` Siva Chandra
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=CAGyQ6gzAv4g8OV+xzawJ6ETFrNJ5qndzwEi9i0KQ76Ha_8u7Ow@mail.gmail.com \
--to=sivachandra@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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