Re: Creating a git branch for cond*

[Jim Porter]

On 1/28/2024 7:36 PM, Eli Zaretskii wrote:
> 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.

One thing I especially hope for with a branch for cond* is that it would 
allow for making backwards-incompatible changes without (much) risk of 
causing problems for users of cond*. I'm open to the possibility that 
cond* is nicer than pcase (for my purposes, anyway), but I'm not sure 
yet. A branch would make it easier for me to track any changes to cond* 
and try my hand at rewriting some pcase-based code to use cond*. Such an 
attempt might reveal some area of improvement for cond*, and it would be 
a shame if it were too late to do anything about it. (Of course, we 
could probably change cond* in backwards-incompatible ways up until 
Emacs 30.1 or so, but I think it'd be nicer for everyone if it were 
mostly-stable by the time it hits master so that people who prefer it 
can start using it without worrying much about breaking changes.)