From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/igc as feature branch
Date: Wed, 03 Jul 2024 15:01:04 -0400 [thread overview]
Message-ID: <yp1y16ii9lb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m25xtmjroo.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Wed, 03 Jul 2024 19:44:55 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Andrea Corallo <acorallo@gnu.org> writes:
>
>> Hi all,
>>
>> given a number of developers here are tracking and working cooperatively
>> on scratch/igc and the aim is to hopefully reach a mergable status,
>> shouldn't we move the development to a feature branch (read
>> feature/igc)?
>>
>> Typically feature branch are supposed to be tracked by other people
>> (read no force push allowed) and commit messages are already in the
>> format suggested by CONTRIBUTE.
>
> Can't speak for Helmut or Pip, but I find it too early to put
> restictions on developers :-).
>
> BTW, what's in for the developers when it becomes a feature branch?
- Tipically the guarantee that the branch is not force pushed (a PITA
for other developers tracking and working on the branch).
- It gives more visibility externally, so overt time more users can find
it, try it, and report issues.
- 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.
It's indeed up to the developers of the branch, I'd personally find it
advantageous therefore my proposal but it's just me :)
next prev parent reply other threads:[~2024-07-03 19:01 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 [this message]
2024-07-03 19:29 ` Gerd Möllmann
2024-07-03 19:37 ` Gerd Möllmann
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=yp1y16ii9lb.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@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.