unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Creating a git branch for cond*
Date: Thu, 25 Jan 2024 16:08:37 +0000	[thread overview]
Message-ID: <ZbKHhXUWiNpZNIu5@ACM> (raw)
In-Reply-To: <864jf1csts.fsf@gnu.org>

Hello, Eli.

On Thu, Jan 25, 2024 at 17:53:51 +0200, Eli Zaretskii wrote:
> > Date: Thu, 25 Jan 2024 15:48:18 +0000
> > From: Alan Mackenzie <acm@muc.de>

> > Hello, Richard, Eli, and Emacs.

> > Richard posted some embryonic code for cond* a little over a week ago.

> > To move things forward, I propose creating the git branch
> > feature/condstar, and incorporating the new code into it in
> > lisp/emacs-lisp/condstar.el.  This will enable its development to happen
> > more systematically and rapidly.

> > Does anybody have any objections?

> You intend to maintain that branch personally?

I'm prepared to do that, yes.

> If you intend for Richard to do that, it's up to him, I think.

Richard will surely respond to my last post.  Let's see what he says.

> Having more than one branch in a repository complicates Git-related
> workflows, and could cause problems if the user pushes to the wrong
> branch.  So it is not an easy decision.

It's clear from my code reviewing so far that cond* is not yet ready for
prime time.  Creating a branch for it would be, I think, the normal
thing in Emacs development.

My main motivation is not to let the current impetus peter out.

But let's see what Richard says.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2024-01-25 16:08 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 [this message]
2024-01-25 16:14     ` Eli Zaretskii
2024-01-29  3:19   ` Richard Stallman
2024-01-29  3:36     ` Eli Zaretskii
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=ZbKHhXUWiNpZNIu5@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --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).