public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 7.6.90 available for testing
Date: Mon, 13 Jan 2014 18:28:00 -0000	[thread overview]
Message-ID: <83wqi368k7.fsf@gnu.org> (raw)
In-Reply-To: <52D427A4.6010704@redhat.com>

> Date: Mon, 13 Jan 2014 17:51:32 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
> 
> On 01/11/2014 08:55 AM, Eli Zaretskii wrote:
> 
> > 
> > This is because of the "-I./../" part on the GCC command line.  My
> > version of GCC doesn't like the trailing slash.
> 
> Guessing that's an old gcc.

Your guess is correct.  (I also tried a newer GCC, and the problem
never happened there.)  But I think that slash is the odd one out
anyway: the other -I arguments don't have it.

> > OK to push the following (with a suitable log entry)?
> 
> Sure.

Thanks.

As this will be my first push when we are branched, what are the
procedures for that with git?  I'm guessing

  git checkout gdb-7.7-branch
  (hack, hack)
  git commit
  git push

Is that correct?  If so, what about doing the same on master -- should
I merge it myself and then push, or are these merges handled in some
other way by someone else?

TIA

  reply	other threads:[~2014-01-13 18:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 10:14 Joel Brobecker
2014-01-08 18:18 ` Reini Urban
2014-01-09  2:46   ` Joel Brobecker
2014-01-09 17:07   ` Tom Tromey
2014-01-10  4:25     ` Joel Brobecker
2014-01-10  1:52   ` Yao Qi
2014-01-09 18:27 ` Regressions on s390x RHEL-6.5 (was: Re: GDB 7.6.90 available for testing) Sergio Durigan Junior
2014-01-11  8:56 ` GDB 7.6.90 available for testing Eli Zaretskii
2014-01-13 17:33   ` Eli Zaretskii
2014-01-13 17:51   ` Pedro Alves
2014-01-13 18:28     ` Eli Zaretskii [this message]
2014-01-13 18:44       ` Pedro Alves
2014-01-13 18:50         ` Eli Zaretskii
2014-01-13 19:15           ` Eli Zaretskii
2014-01-13 19:53             ` Pedro Alves
2014-01-13 20:33               ` Eli Zaretskii
2014-01-15 16:33               ` Eli Zaretskii
2014-01-13 10:29 ` Ricard Wanderlof
2014-01-13 10:37   ` Joel Brobecker

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=83wqi368k7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).