git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leo Razoumov" <slonik.az@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Andreas Ericsson" <ae@op5.se>, git@vger.kernel.org
Subject: Re: [PATCH] git-fetch should not strip off ".git" extension
Date: Tue, 21 Oct 2008 06:23:57 -0400	[thread overview]
Message-ID: <ee2a733e0810210323j249c3460x881af6d6aefc647c@mail.gmail.com> (raw)
In-Reply-To: <7vzlkz2jv7.fsf@gitster.siamese.dyndns.org>

On 10/20/08, Junio C Hamano <gitster@pobox.com> wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
>  >>...
>
> >>
>  >>  builtin-fetch--tool.c |    2 --
>  >>  builtin-fetch.c       |    2 --
>  >>  2 files changed, 0 insertions(+), 4 deletions(-)
>  >>
>  >> diff --git a/builtin-fetch--tool.c b/builtin-fetch--tool.c
>  >> index 7460ab7..5d0b95f 100644
>  >> --- a/builtin-fetch--tool.c
>  >> +++ b/builtin-fetch--tool.c
>  >> @@ -160,8 +160,6 @@ static int append_fetch_head(FILE *fp,
>  >>      for (i = remote_len - 1; remote[i] == '/' && 0 <= i; i--)
>  >>              ;
>  >>      remote_len = i + 1;
>  >> -    if (4 < i && !strncmp(".git", remote + i - 3, 4))
>  >> -            remote_len = i - 3;
>  >>
>  >>      note_len = 0;
>  >>      if (*what) {
>  >> diff --git a/builtin-fetch.c b/builtin-fetch.c
>  >> index ee93d3a..28123a5 100644
>  >> --- a/builtin-fetch.c
>  >> +++ b/builtin-fetch.c
>  >> @@ -348,8 +348,6 @@ static int store_updated_refs(const char *url,
>  >> const char *remote_name,
>  >>              for (i = url_len - 1; url[i] == '/' && 0 <= i; i--)
>  >>                      ;
>  >>              url_len = i + 1;
>  >> -            if (4 < i && !strncmp(".git", url + i - 3, 4))
>  >> -                    url_len = i - 3;
>  >>
>  >
>  > Will this still play nicely with
>  >
>  >   git clone foo.git
>  >
>  > ?
>
>
> I think it would.
>
>  As far as I can tell, the only thing the patch changes is to disable the
>  long established "repository name clean-up" feature in the autogenerated
>  merge messages (iow, input to "fmt-merge-msg").

Even though the old behavior is "long established", it introduces
unnecessary ambiguity. If I have two repos

(1) Foo      #private repo where I do my daily work
(2) Foo.git #exported public repo

the current behavior makes git messages confuse the repos.

--Leo--

  reply	other threads:[~2008-10-21 10:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 11:59 [PATCH] git-fetch should not strip off ".git" extension Leo Razoumov
2008-10-20 10:36 ` Andreas Ericsson
2008-10-20 15:08   ` Leo Razoumov
2008-10-20 18:37   ` Junio C Hamano
2008-10-21 10:23     ` Leo Razoumov [this message]
2008-10-21 16:56       ` Junio C Hamano
2008-10-21 22:06         ` Alex Riesen
2008-10-21 22:36           ` Junio C Hamano
2008-10-21 22:43             ` Alex Riesen
2008-10-22  7:55               ` Andreas Ericsson
2008-10-21 23:35             ` Junio C Hamano
2008-10-22 11:35             ` Leo Razoumov
2008-10-22 11:50             ` Leo Razoumov

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=ee2a733e0810210323j249c3460x881af6d6aefc647c@mail.gmail.com \
    --to=slonik.az@gmail.com \
    --cc=ae@op5.se \
    --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).