Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: contribution checklist in the wiki
Date: Wed, 22 May 2013 10:23:00 -0000	[thread overview]
Message-ID: <20130522102337.GB4017@adacore.com> (raw)
In-Reply-To: <519C99F8.1000206@redhat.com>

> 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

I don't want to open a debate over this, as we would first need
to switch to git in order for me to make a possibly-compelling
argument in favor of getting rid of them. But the reason why I got
rid of them at AdaCore is that git log has become a much more
powerful way to perform searches (you can limit the output using
criteria such as dates, or author, for instance). In the meantime,
they stopped getting in the way, as they were are a constant source
of merge/cherry-pick conflicts.

-- 
Joel


  reply	other threads:[~2013-05-22 10:23 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
2013-05-22 10:23             ` Joel Brobecker [this message]
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=20130522102337.GB4017@adacore.com \
    --to=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