unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Edward Steere <edward.steere@gmail.com>
To: David Engster <deng@randomsample.de>
Cc: "Charles A. Roelli" <charles@aurox.ch>, 28878@debbugs.gnu.org
Subject: bug#28878: CEDET merge bug
Date: Fri, 20 Oct 2017 18:46:12 +0200	[thread overview]
Message-ID: <CAMz5G58aJaCrdxV7LfJYVnjN6-PFe+h608F9t73q_xZ8omHV+w@mail.gmail.com> (raw)
In-Reply-To: <871sm0wl6m.fsf@engster.org>

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

>
> Yes, tests are excluded.


I'll make some time to take a look at the tests again.

>> It only needs
> >> ChangeLogs for the byte-compiler warning fixes.
> >
> > Are you referring to the following two commits?
> >
> > d2a57bdfec * scratch/last-cedet-merge origin/scratch/last-cedet-merge
> CEDET:
> > Fix "unknown slot [...]"  warnings
> > 9c2feacc85 * CEDET: Fix "obsolete name arg [...] to constructor" warnings
>
> Yes.
>

I'll try to take a look at this as well.

I count 165 commits since the last merge when I look at cedet.git
and I only see 49 commits in emacs.git from your work on the
merge.  What about the other 116 commits?  I'm counting from
f36f29b0 on cedet.git.

[-- Attachment #2: Type: text/html, Size: 1498 bytes --]

  reply	other threads:[~2017-10-20 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 18:43 bug#28878: CEDET merge bug Charles A. Roelli
2017-10-17 20:40 ` David Engster
2017-10-18  5:38   ` Edward Steere
2017-10-18 15:05     ` David Engster
2017-10-20 16:46       ` Edward Steere [this message]
2017-10-20 20:40         ` David Engster
2017-10-26 18:31           ` Charles A. Roelli
2019-11-08  4:14           ` bug#23792: " Stefan Kangas
2019-11-10  7:48             ` Edward Steere
2019-11-10 21:07               ` bug#23792: " Stefan Kangas
2019-11-11  0:11                 ` Eric Ludlam
2019-11-11  2:07                   ` bug#23792: " Stefan Kangas
2019-11-16  8:49             ` David Engster

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMz5G58aJaCrdxV7LfJYVnjN6-PFe+h608F9t73q_xZ8omHV+w@mail.gmail.com \
    --to=edward.steere@gmail.com \
    --cc=28878@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=deng@randomsample.de \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).