From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Gennady Uraltsev <gennady.uraltsev@gmail.com>, git@vger.kernel.org
Subject: Re: Bug in git-remote
Date: Mon, 17 Dec 2018 13:50:56 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1812171347530.43@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20181215130204.GZ30222@szeder.dev>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
Hi Gábor,
On Sat, 15 Dec 2018, SZEDER Gábor wrote:
> On Sat, Dec 15, 2018 at 02:14:56AM -0500, Gennady Uraltsev wrote:
> > I am on git version 2.20.0
> >
> > $ git remote
> >
> > does not show remotes configured in named files in $GIT_DIR/remotes/
> >
> > I do not think that this is the intended behavior.
>
> It's a known bug. When 'git remote' was rewritten as a builtin
> command in C in commit 211c89682e (Make git-remote a builtin,
> 2008-02-29) the parts dealing with remotes under 'GIT_DIR/remotes/'
> were not rewritten. I don't know whether that was intended or not,
> but storing remote information as configuration was about two years
> old back then. Given that since then '$GIT_DIR/remotes/' got marked
> as "This mechanism is legacy and not likely to be found in modern
> repositories", I'm not sure it's worth fixing. Perhaps it's time for
> calling it deprecated.
I would be in favor of deprecating it, and then removing it.
However, when I tried a similar thing with the completely obsolete
`$GIT_DIR/branches/` feature, it was shot down IIRC on the mere suspicion
that there was a single remaining user among the Linux kernel lieutenants.
And I fear that the suspected workflow of that lieutenant involved having
those legacy remotes, too.
Hopefully this issue will be resolved somehow, as it is not exactly a
splendid idea to keep a legacy feature of a software used by millions,
just for a single user, I would think.
Ciao,
Dscho
>
>
> > In particular:
> >
> > $ git init --bare test.git
> > Initialized empty Git repository in /home/guraltsev/admin/test/git/test.git/
> >
> > $ cd test.git
> >
> > $ mkdir -p remotes
> > mkdir: created directory 'remotes'
> >
> > $ echo -e "URL: /testremote.git \n Push: *:* \n Pull:
> > refs/heads/*:refs/remotes/testremote/* " > remotes/testremote
> >
> > $ git remote
> >
> > $ git remote show testremote
> > fatal: '/testremote.git' does not appear to be a git repository
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
> >
> >
> >
> > The second to last command should show testremote as a remote.
> >
> >
> > Best,
> >
> > Gennady
> >
>
>
>
>
next prev parent reply other threads:[~2018-12-17 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 7:14 Bug in git-remote Gennady Uraltsev
2018-12-15 13:02 ` SZEDER Gábor
2018-12-17 12:50 ` Johannes Schindelin [this message]
2018-12-28 12:32 ` SZEDER Gábor
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1812171347530.43@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=gennady.uraltsev@gmail.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/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://80x24.org/mirrors/git.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).