From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Add missing branchpoints to gdb.git?
Date: Fri, 19 Aug 2011 22:08:00 -0000 [thread overview]
Message-ID: <20110819220746.GC11620@adacore.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-08-19 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 18:02 Joel Brobecker
2011-08-19 20:37 ` Andreas Schwab
2011-08-19 22:08 ` Joel Brobecker [this message]
2011-08-19 23:35 ` Andreas Schwab
2011-08-22 16:23 ` Tom Tromey
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=20110819220746.GC11620@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
/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