This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Add missing branchpoints to gdb.git?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 19 Aug 2011 15:07:46 -0700
- Subject: Re: Add missing branchpoints to gdb.git?
- References: <20110819180206.GA11620@adacore.com> <m2zkj59lz0.fsf@igel.home>
> > gdb_7_2-2010-07-07-branchpoint: cd4c6c46d781fe20f1a73c9e07c0fbc05bfc8a0c
> > gdb_7_1-2010-02-18-branchpoint: e16b3828eafec635405cc34beb8f08db117d7331
> > gdb_7_0-2009-09-16-branchpoint: a4a5c910c73f0bf2b7d063912274461838139423
>
> Actually, the real branch points are
> b2f5cf460a3e550ab4032be1a90c752c0b9bdd9f,
> 9a4b7643da53df33552a50d9f02ddf5be5aef883,
> fe78766a0c9eea331e2a1799027f2f7c8e990ff8, resp.
How did you come up with those commit IDs? I used `git merge-base',
and looking at the output, it seemed right. For instance, for the 7.2
branchpoint, I had cd4c6c46d781fe20f1a73c9e07c0fbc05bfc8a0c, which in
fact is a parent of the commit you are proposing. And since git confirms
that my commit is on the master branch as well, I figured it has to be
a more likely branchpoint?
--
Joel