Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, Gary Benson <gbenson@redhat.com>,
	Stan Shebs <stanshebs@earthlink.net>,
	gdb@sourceware.org
Subject: Re: Patchwork patch tracking system
Date: Wed, 21 May 2014 17:49:00 -0000	[thread overview]
Message-ID: <20140521174908.GP22794@adacore.com> (raw)
In-Reply-To: <537CDFCE.7000407@redhat.com>

> I'm not certain that would work for us, unless we change some process.
> I am under the impression that that matches commits by git hash.
> The fact that the ChangeLog is usually not a part of the patch
> and then is added before push changes the hash.  Also,
> given we only allow fast-forward, it's very frequent that patches
> need to be rebased when pushed, which changes hash as well.

I think we should be open to the idea of changing our process to
some degree. To me, keeping track of patch series, in terms of
grouping as well as iterations of the patch series, would be
a great feature worth some changes in our procedures. To go
even further, I am not necessarily attached to making email-based
interaction the primary way of discussing an email. I know many
people are, and I am not advocating for one way or the other, but
just trying to show that this isn't an obvious requirement to me.

-- 
Joel


  reply	other threads:[~2014-05-21 17:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 10:08 Gary Benson
2014-04-04 22:50 ` Stan Shebs
2014-04-17 18:18   ` Gary Benson
2014-04-22 15:40     ` Joel Brobecker
2014-04-22 15:51       ` Eric Christopher
2014-04-22 18:37         ` Joel Brobecker
2014-04-24 11:42           ` Siva Chandra
2014-08-02 14:25             ` Mike Frysinger
2014-04-29 17:25       ` Tom Tromey
2014-04-29 17:36         ` Eli Zaretskii
2014-04-29 18:58         ` Joel Brobecker
2014-04-30  9:19           ` Gary Benson
2014-04-30 12:45             ` Joel Brobecker
2014-04-29 19:33         ` Pedro Alves
2014-04-29 22:32           ` Breazeal, Don
2014-04-30  1:08             ` Pedro Alves
2014-04-30  3:45               ` Breazeal, Don
2014-05-21 14:47         ` Tom Tromey
2014-05-21 17:18           ` Pedro Alves
2014-05-21 17:49             ` Joel Brobecker [this message]
2014-05-21 18:03             ` Eli Zaretskii
2014-05-21 18:23               ` Joel Brobecker
2014-05-21 18:48                 ` Eli Zaretskii
2014-05-21 19:45                   ` Joel Brobecker
2014-05-21 21:35               ` Pedro Alves

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=20140521174908.GP22794@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gbenson@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@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