From: "Alex Riesen" <raa.lkml@gmail.com>
To: "J Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Fix the remote note the fetch-tool prints after storing a fetched reference
Date: Wed, 6 Jun 2007 13:27:57 +0200 [thread overview]
Message-ID: <81b0412b0706060427l1846bde7racabcfea5d15bdb4@mail.gmail.com> (raw)
In-Reply-To: <7vps495uvs.fsf@assigned-by-dhcp.cox.net>
On 6/6/07, J Junio C Hamano <gitster@pobox.com> wrote:
> > Which one was fetched when? /home/user/a or /home/user/a.git?
>
> I am half tempted to say that this is very close to "doctor, it
> confuses me when I have both of them". Imagine the case where
> the source were a remote repository _and_ there was no way other
> than interacting with it via git protocol. You cannot really
> tell (well, you can tell half, by trying both and if a worked
> but a.git didn't you can tell that a.git does not exist) nor you
> do not really care.
Of course you can! Just print the path to the remote EXACTLY
how the user entered it!
> > Besides, I just noticed git-clone is broken WRT the .git
> > as well: I can clone a "a.git" into "b" (and it ignores -l and -s!),
> > but I can't fetch the "a" (aka "origin") being in "b". And of
> > course, "origin" in "b" is setup as "/path/a", not "/path/a.git".
>
> This probably is worth fixing, independent from what the message
> says before or after your patch.
And "probably" means: it is broken, but this is ok?
next prev parent reply other threads:[~2007-06-06 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 7:45 [PATCH] Fix the remote note the fetch-tool prints after storing a fetched reference Alex Riesen
2007-06-06 8:14 ` Junio C Hamano
2007-06-06 8:42 ` Alex Riesen
2007-06-06 8:50 ` J Junio C Hamano
2007-06-06 11:27 ` Alex Riesen [this message]
2007-06-06 19:28 ` Junio C Hamano
2007-06-06 15:52 ` Alex Riesen
2007-06-06 20:07 ` Junio C Hamano
2007-06-06 22:48 ` Alex Riesen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0706060427l1846bde7racabcfea5d15bdb4@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).