From: Thomas Rast <trast@student.ethz.ch>
To: Brent Goodrick <bgoodr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: "warning: no common commits" triggered due to change of remote's IP address?
Date: Mon, 2 Mar 2009 09:40:21 +0100 [thread overview]
Message-ID: <200903020940.24813.trast@student.ethz.ch> (raw)
In-Reply-To: <e38bce640903011501t2c7a134dp887f5a96db3db0f4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
Brent Goodrick wrote:
> On Sun, Mar 1, 2009 at 1:20 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> > [...] have you rewritten the repo hosting 'home' between
> > two fetches? Using (especially, but not only) git-filter-branch can
> > easily render your history disjoint from the pre-filtering state.
>
> Hmmm, maybe, without knowing it.
It's rather hard to rewrite history without knowing it, there are big
warnings all over the relevant tools' manpages...
> Originally, that section of the
> .git/config file had "*"'s where "home" was. To clarify, the original
> was:
>
> [remote "origin"]
> url = <some_ip_address>:git.repos/environ.git
> fetch = +refs/heads/*:refs/remotes/origin/*
>
> and the current one is now:
>
> [remote "origin"]
> url = <some_ip_address>:git.repos/environ.git
> fetch = +refs/heads/home:refs/remotes/origin/home
>
> Maybe I had made that change and this is the first time I am doing a
> fetch to using that change. I thinking that was the cause of this,
> because I retried doing a fetch into a separate throw-away repo with
> just the change of IP address, and it did not need to fetch anything
> more. I had not executed git-filter-branch at all.
Ironically I cannot reproduce this except with my "own" version that
includes the patch I posted yesterday. I'll have to look into why it
fails to list any refs to the remote. In the meantime please
disregard that patch.
If you still have a repo that can reproduce the problem, please keep a
copy for future investigation, and then try
git fetch-pack -v $url refs/remotes/origin/home 2>&1 \
| git name-rev --stdin
The -v will dump a lot of output about the common commit search. The
message "giving up" indicates that you hit the 256 commit limit; if
that doesn't appear, please include the full output so that we can see
where it stops.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-02 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 18:01 "warning: no common commits" triggered due to change of remote's IP address? Brent Goodrick
2009-03-01 21:20 ` Thomas Rast
2009-03-01 23:01 ` Brent Goodrick
2009-03-02 8:40 ` Thomas Rast [this message]
2009-03-02 8:56 ` Thomas Rast
2009-03-02 16:43 ` Brent Goodrick
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=200903020940.24813.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=bgoodr@gmail.com \
--cc=git@vger.kernel.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.
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).