all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Brian Leung <leungbk@posteo.net>, 59921@debbugs.gnu.org
Subject: bug#59921: 30.0.50; emacs HEAD is missing some older emacs-29 commits
Date: Fri, 9 Dec 2022 04:28:25 -0800	[thread overview]
Message-ID: <CADwFkm=oKSwQFS=MziY7+J23HZYeYX6NwtjiMs0Qw8YROqt8QQ@mail.gmail.com> (raw)
In-Reply-To: <87r0x8rie6.fsf@posteo.net>

Brian Leung <leungbk@posteo.net> writes:

> For example,
> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=c83c95634e7a8d0f334ac5d45eebf357e413906c
> and
> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=b710ca62c00ef90a46fc90a9ae06fdf3bba87bc2
> are not in Emacs 30, at the time of writing, whereas some newer Emacs 29
> commits are on master.

Here's what I see:

$ git fetch
[...]
$ git branch -a --contains b710ca62c00ef90a46fc90a9ae06fdf3bba87bc2 |
grep master
  master
  remotes/origin/HEAD -> origin/master
  remotes/origin/master
$ git branch -a --contains c83c95634e7a8d0f334ac5d45eebf357e413906c |
grep master
  master
  remotes/origin/HEAD -> origin/master
  remotes/origin/master

Doesn't this mean that these commits are on the master branch?





  parent reply	other threads:[~2022-12-09 12:28 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 [this message]
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
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='CADwFkm=oKSwQFS=MziY7+J23HZYeYX6NwtjiMs0Qw8YROqt8QQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=59921@debbugs.gnu.org \
    --cc=leungbk@posteo.net \
    /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.