From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: lost again on syntax change - local repository?
Date: 28 Nov 2005 05:09:40 -0800 [thread overview]
Message-ID: <86d5kk7wbv.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051128104831.GN22159@pasky.or.cz>
>>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:
Petr> Dear diary, on Mon, Nov 28, 2005 at 03:01:18AM CET, I got a letter
Petr> where "Randal L. Schwartz" <merlyn@stonehenge.com> said that...
>> localhost:..Git/Play/local.git % cg-branch-add origin "$(cd ..; pwd)/remote.git#master"
Petr> BTW, it should be fine to just say ../remote.git#master.
Maybe this is why yours worked.
Ahh, yes, it did.
So, cg-push treats '../..' differently from '/foo/bar/...'.
This is bad. That's the bug.
cg-push treats "../" as a local filesystem, and "/..." as git-ssh.
This is a change from before.
Please make it recognize "/..." as a local file again.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-28 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 2:01 lost again on syntax change - local repository? Randal L. Schwartz
2005-11-28 5:11 ` Junio C Hamano
2005-11-28 6:36 ` Alecs King
2005-11-28 13:04 ` Randal L. Schwartz
2005-11-28 10:48 ` Petr Baudis
2005-11-28 13:09 ` Randal L. Schwartz [this message]
2005-11-28 13:41 ` Petr Baudis
2005-11-28 13:45 ` Randal L. Schwartz
2005-11-28 13:59 ` Randal L. Schwartz
2005-11-28 14:34 ` Petr Baudis
2005-11-28 14:46 ` Randal L. Schwartz
2005-11-28 19:15 ` Petr Baudis
2005-11-28 19:25 ` Randal L. Schwartz
2005-11-28 20:53 ` Petr Baudis
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=86d5kk7wbv.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).