all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/igc as feature branch
Date: Wed, 03 Jul 2024 21:37:42 +0200	[thread overview]
Message-ID: <m2h6d6s1vd.fsf@pro2.fritz.box> (raw)
In-Reply-To: <m2le2is28i.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Wed, 03 Jul 2024 21:29:49 +0200")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Andrea Corallo <acorallo@gnu.org> writes:
>
>> - The fact that the branch is already worked with commits that will be
>> directly mergable without having to do a mega rebase afterward.  Also
>> the mega rebase would cancel all or part of the history which I find a
>> serious disadvantage.
>
> Hm, that makes me curious.
>
> Does it mean that in the end, before merging, every commit must have a
> conforming commit message? Also, there are probably many hundreds of
> commits that are not in scratch/igc at all, but only in my original.
> What's with those?

Some numbers, hope I got the git right

/Users/gerd/emacs/github/igc % git rev-list --count cl-packages..igc --first-parent
980

/Users/gerd/emacs/savannah/igc % git rev-list --count master..scratch/igc --first-parent
431



  reply	other threads:[~2024-07-03 19:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 12:40 scratch/igc as feature branch Andrea Corallo
2024-07-03 17:44 ` Gerd Möllmann
2024-07-03 19:01   ` Andrea Corallo
2024-07-03 19:29     ` Gerd Möllmann
2024-07-03 19:37       ` Gerd Möllmann [this message]
2024-07-04  4:58         ` Eli Zaretskii
2024-07-04  6:19           ` Gerd Möllmann
2024-07-03 22:04       ` Andrea Corallo
2024-07-04  4:15         ` Gerd Möllmann
2024-07-04  6:15           ` Eli Zaretskii
2024-07-04  4:49       ` Eli Zaretskii
2024-07-04  6:14         ` Gerd Möllmann
2024-07-04  6:26           ` Eli Zaretskii
2024-07-04  6:55             ` Gerd Möllmann
2024-07-04  7:41               ` 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=m2h6d6s1vd.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.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.
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.