From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Feedback on scratch/igc Branch
Date: Wed, 23 Oct 2024 23:40:54 +0300 [thread overview]
Message-ID: <ZxlfVrZUe5hjQYtq@lco2> (raw)
In-Reply-To: <86h692enlw.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2024-10-23 20:28]:
> > Date: Wed, 23 Oct 2024 16:22:11 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: Eval EXEC <execvy@gmail.com>, emacs-devel@gnu.org
> >
> > * Eli Zaretskii <eliz@gnu.org> [2024-09-08 08:47]:
> > > It's IMO too early to talk about landing this on master. We still
> > > have unresolved issues, like what to do with signals delivered to
> > > Emacs when MPS is collecting garbage and the arena is locked. We also
> > > need to decide whether we want to fork MPS and make changes in it on
> > > our own or not.
> >
> > I see no scratch/igc branch, how do I get it?
>
> "git pull" followed by "git checkout scratch/igc".
$ git checkout scratch/igc
error: pathspec 'scratch/igc' did not match any file(s) known to git
I cannot see that branch.
next prev parent reply other threads:[~2024-10-23 20:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 5:26 Feedback on scratch/igc Branch Eval EXEC
2024-09-08 5:46 ` Eli Zaretskii
2024-10-23 13:22 ` Jean Louis
2024-10-23 17:27 ` Eli Zaretskii
2024-10-23 20:40 ` Jean Louis [this message]
2024-10-23 22:17 ` Philip Kaludercic
2024-10-24 19:11 ` Jean Louis
2024-10-24 6:51 ` Eli Zaretskii
2024-10-24 7:46 ` tomas
2024-10-24 19:14 ` Jean Louis
2024-10-24 19:21 ` tomas
2024-10-24 20:26 ` Andreas Schwab
2024-10-25 6:24 ` Eli Zaretskii
2024-10-25 8:06 ` Andreas Schwab
2024-10-25 10:15 ` Eli Zaretskii
2024-11-01 19:31 ` Jean Louis
2024-11-01 20:02 ` Eli Zaretskii
2024-11-02 7:19 ` Jean Louis
2024-11-02 9:06 ` Jean Louis
2024-11-02 22:34 ` Jean Louis
2024-11-01 19:30 ` Jean Louis
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=ZxlfVrZUe5hjQYtq@lco2 \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).