Re: scratch/igc: Keeping a TODO list?

[Eli Zaretskii]

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: eller.helmut@gmail.com,  pipcet@protonmail.com,  stefankangas@gmail.com,
>   emacs-devel@gnu.org,  gerd@gnu.org
> Date: Mon, 13 Jan 2025 14:16:03 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> >> Cc: Eli Zaretskii <eliz@gnu.org>,  pipcet@protonmail.com,
> >>   stefankangas@gmail.com,  emacs-devel@gnu.org,  gerd@gnu.org
> >> Date: Mon, 13 Jan 2025 05:37:19 +0100
> >> 
> >> Helmut Eller <eller.helmut@gmail.com> writes:
> >> 
> >> > On Sun, Jan 12 2025, Eli Zaretskii wrote:
> >> >
> >> >>> From: Helmut Eller <eller.helmut@gmail.com>
> >> >>> Here are some of mine:
> >> >>
> >> >> Do you think any of these must be done before we land the branch?
> >> >
> >> > No.  I think that the people who decide what ends up in master don't
> >> > care much about these items.
> >> 
> >> Sometimes I think we should make another branch that is a real scratch
> >> branch again.
> >
> > Does this mean you think the igc branch is not yet ready to consider
> > it for landing on master, and should remain a scratch experimental
> > branch for longer?
> 
> It means I don't care much if scratch/igc gets merged, and that it
> would be more interesting if some of the usual suspects could do more
> interesting stuff on a different branch.

Well, we usually develop features so we could land them later.

You can always start a new scratch branch if you need to do something
experimental.