From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: Creating a git branch for cond*
Date: Mon, 29 Jan 2024 05:36:23 +0200 [thread overview]
Message-ID: <86o7d44xqg.fsf@gnu.org> (raw)
In-Reply-To: <E1rUIBA-0007ZW-Ti@fencepost.gnu.org> (message from Richard Stallman on Sun, 28 Jan 2024 22:19:24 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: acm@muc.de, emacs-devel@gnu.org
> Date: Sun, 28 Jan 2024 22:19:24 -0500
>
> cond* is just one file, and no change in anyplace else is needed to
> get it working and make it usable. So there should be no need for a
> branch for it.
The idea was to keep it on a branch until we decide it is ready to
land on master. Having it on a branch will allow to work on
finilizing it more conveniently. This includes solving any
significant issues and adding documentation. I would prefer to keep
it on a branch during this (hopefully, short) period, since that would
allow us to keep its history afterwards, and will also avoid the
need to send whole files each time something changes.
Alan offered his technical help in managing this vis-a-vis Git, so you
personally don't need to worry about these aspects. But for us,
having cond* on a branch during this period is a significant
advantage.
next prev parent reply other threads:[~2024-01-29 3:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:48 Creating a git branch for cond* Alan Mackenzie
2024-01-25 15:53 ` Eli Zaretskii
2024-01-25 16:08 ` Alan Mackenzie
2024-01-25 16:14 ` Eli Zaretskii
2024-01-29 3:19 ` Richard Stallman
2024-01-29 3:36 ` Eli Zaretskii [this message]
2024-01-29 3:51 ` Jim Porter
2024-02-02 3:40 ` Richard Stallman
2024-02-02 7:17 ` Eli Zaretskii
2024-01-25 16:16 ` Alfred M. Szmidt
2024-01-25 16:37 ` Alan Mackenzie
2024-01-25 16:49 ` Alfred M. Szmidt
2024-01-25 16:56 ` Eli Zaretskii
2024-01-25 17:57 ` Alan Mackenzie
2024-01-25 19:47 ` Stefan Kangas
2024-01-25 20:08 ` Alan Mackenzie
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=86o7d44xqg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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).