Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] bad VER in src-release causes snapshot failure
Date: Mon, 22 Jul 2013 15:18:00 -0000	[thread overview]
Message-ID: <20130722151758.GA4944@adacore.com> (raw)
In-Reply-To: <87ip0eo63j.fsf@fleche.redhat.com>

> Joel> I also meant to mention that my patch avoids duplicating again
> Joel> the code used to compute the GDB version... It's already spread
> Joel> everywhere, so not a big deal, but relatively easy to avoid by
> Joel> re-using your create-version.sh script. A bit of a hack, though.
> 
> Thanks Joel.  That seems like a decent rationale to me.
> I'm ok with your patch.

OK, thanks Tom. Patch now applied. Hopefully we'll have our nightly
snapshots again tonight.

-- 
Joel


      reply	other threads:[~2013-07-22 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 15:34 Joel Brobecker
2013-07-11 16:17 ` Tom Tromey
2013-07-11 16:42   ` Joel Brobecker
2013-07-11 16:45     ` Joel Brobecker
2013-07-13 15:03       ` Tom Tromey
2013-07-22 15:18         ` Joel Brobecker [this message]

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=20130722151758.GA4944@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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