This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.6.90 available for testing
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: brobecker at adacore dot com, gdb-patches at sourceware dot org
- Date: Mon, 13 Jan 2014 20:27:52 +0200
- Subject: Re: GDB 7.6.90 available for testing
- Authentication-results: sourceware.org; auth=none
- References: <20140108101428 dot C2280E003F at joel dot gnat dot com> <831u0ec2y6 dot fsf at gnu dot org> <52D427A4 dot 6010704 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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