From: tomas@tuxteam.de
To: emacs-devel@gnu.org
Subject: Re: Feedback on scratch/igc Branch
Date: Thu, 24 Oct 2024 21:21:21 +0200 [thread overview]
Message-ID: <ZxqeMRy240o+8X5J@tuxteam.de> (raw)
In-Reply-To: <ZxqckHlWY3NeGPS2@lco2>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On Thu, Oct 24, 2024 at 10:14:24PM +0300, Jean Louis wrote:
> * tomas@tuxteam.de <tomas@tuxteam.de> [2024-10-24 10:48]:
> > The error message gives me the impression that git is trying to
> > interpret "scratch/igc" as a file path and not as a branch. So
> > that might be due to some uncommon/unexpected configuration on
> > OP's side.
> >
> > Jean-Louis: what does the command
> >
> > git branch -a
> >
> > say on your side?
>
> * remotes/origin/scratch/hard-narrow
> * remotes/origin/scratch/highlight-n-windows
> * remotes/origin/scratch/isearch-show-toggles
> * remotes/origin/scratch/jit-lock-antiblink
> * remotes/origin/scratch/jit-lock-antiblink-cleaned-up
> * remotes/origin/scratch/joaot/make-completion-at-point-function
>
> That is where I expected "igc" to be alphabetically sorted, is not there.
Hm. But it seems to be there:
tomas@trotzki:~$ git ls-remote --heads git://git.sv.gnu.org/emacs.git | grep igc
d864c26b207362b4591dc821fe8bae1394c61281 refs/heads/scratch/igc
For some reason your clone isn't fetching it, At the moment I'm
out of ideas on why.
Cheers
--
tomás
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-10-24 19:21 UTC|newest]
Thread overview: 15+ 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
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 [this message]
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
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=ZxqeMRy240o+8X5J@tuxteam.de \
--to=tomas@tuxteam.de \
--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).