From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: sivachandra@google.com, palves@redhat.com,
gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [RFA] - Improve suggestions for generating patches in CONTRIBUTE
Date: Tue, 17 Apr 2012 15:48:00 -0000 [thread overview]
Message-ID: <201204171541.q3HFfMfI004269@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20120417145452.GL2852@adacore.com> (message from Joel Brobecker on Tue, 17 Apr 2012 07:54:52 -0700)
> Date: Tue, 17 Apr 2012 07:54:52 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> > 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.
>
> I am OK with your version. I think this part is considered
> documentation and is more Eli's domain, so please wait for his
> approval.
>
> I also think that 2 GMs agreeing to remove "diff -cp" is enough
> to proceed, but I can take care of removing this part once your
> patch is in. I don't want you to keep flip-flopping just because
> of me.
Make that 3. Tristan's recent darwin diffs made me realise that I've
completely lost the skill to read diff -c output.
next prev parent reply other threads:[~2012-04-17 15:42 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
2012-04-17 15:11 ` Joel Brobecker
2012-04-17 15:48 ` Mark Kettenis [this message]
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=201204171541.q3HFfMfI004269@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sivachandra@google.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