From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: contribution checklist in the wiki
Date: Wed, 22 May 2013 10:12:00 -0000 [thread overview]
Message-ID: <519C99F8.1000206@redhat.com> (raw)
In-Reply-To: <20130522062931.GA4017@adacore.com>
On 05/22/2013 07:29 AM, Joel Brobecker wrote:
>> Now we just need to convince others. :-)
>
> Next thing we know, we will be getting rid of ChangeLog files also :-)
> (which I have done for the AdaCore version, btw)
That I'm not so sure. I do find them useful for archaeology. My
current view mirrors Alexandre's here, so I'll just make his words
mine :-) :
http://sourceware.org/ml/libc-alpha/2013-04/msg00100.html
>
>> As someone that has done _lots_ of archaeology on gdb's code,
>> including going further back beyond the cvs import, I've often
>> had trouble matching ChangeLogs to mailing list discussions, and
>> then often will still not find a clear rationale if I actually
>> find a match. I can only wish people had been doing it too
>> "back then".
>
> Same on my end - I constantly go back in history, both with the FSF
> and AdaCore repositories, and found that they help tremendously.
>
--
Pedro Alves
next prev parent reply other threads:[~2013-05-22 10:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 16:37 Pedro Alves
2013-05-20 10:06 ` Joel Brobecker
2013-05-20 15:14 ` Pedro Alves
2013-05-21 5:26 ` Joel Brobecker
2013-05-21 17:55 ` Pedro Alves
2013-05-22 6:29 ` Joel Brobecker
2013-05-22 10:12 ` Pedro Alves [this message]
2013-05-22 10:23 ` Joel Brobecker
2013-05-22 10:38 ` Pedro Alves
2013-05-22 10:50 ` Joel Brobecker
2013-05-22 14:56 ` Eli Zaretskii
2013-05-20 10:22 ` Hui Zhu
2013-05-20 14:44 ` Pedro Alves
2013-05-20 17:02 ` Doug Evans
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=519C99F8.1000206@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox