From: Eli Zaretskii <eliz@gnu.org>
To: Brian Leung <leungbk@posteo.net>
Cc: stefankangas@gmail.com, 59921@debbugs.gnu.org
Subject: bug#59921: 30.0.50; emacs HEAD is missing some older emacs-29 commits
Date: Sat, 10 Dec 2022 09:22:51 +0200 [thread overview]
Message-ID: <83zgbvyb78.fsf@gnu.org> (raw)
In-Reply-To: <877cz0qo5j.fsf@posteo.net> (message from Brian Leung on Fri, 09 Dec 2022 21:08:40 +0000)
> From: Brian Leung <leungbk@posteo.net>
> Cc: stefankangas@gmail.com, 59921@debbugs.gnu.org
> Date: Fri, 09 Dec 2022 21:08:40 +0000
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I arrived at a similar conclusion using Magit. I don't have a
> >> great understanding of Git, so my best guess is that
> >> 64c7b57ae72
> >> somehow skipped over more commits than expected. You can verify
> >> that the changes corresponding to the missing commits are
> >> present
> >> in the emacs-29 branch but not in master.
> >
> > How did you detect the missing changes in the first place?
>
> I was working in one of the files and noticed that a change I knew
> had been made to that file wasn't there.
That's "a change", in singular. But your original message quoted two
commits, not one. Were both of the discovered by accident?
next prev parent reply other threads:[~2022-12-10 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 10:17 bug#59921: 30.0.50; emacs HEAD is missing some older emacs-29 commits Brian Leung
2022-12-09 10:46 ` Brian Leung
2022-12-09 11:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-09 12:01 ` Brian Leung
2022-12-09 12:28 ` Stefan Kangas
2022-12-09 12:43 ` Brian Leung
2022-12-09 15:54 ` Eli Zaretskii
2022-12-09 21:08 ` Brian Leung
2022-12-10 7:22 ` Eli Zaretskii [this message]
2022-12-10 0:43 ` Brian Leung
2022-12-10 7:52 ` Eli Zaretskii
2022-12-10 11:30 ` Eli Zaretskii
2022-12-10 11:36 ` Brian Leung
2022-12-10 14:22 ` Eli Zaretskii
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=83zgbvyb78.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59921@debbugs.gnu.org \
--cc=leungbk@posteo.net \
--cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.