;
b=GD7WcL8wrupvOatilN4PlIfoBy1WHzc51qaTEuacLjyY886ZHhhuJTIjWYdDdbWJpP
gXwC2SGWuEne7bPCWaauRuEo563qNLpvHf7F/N3CthIvbAUfKUu0hV3CeYPyP1jJGNHr
QcC0uR3pxBz2ymmmnRc67UQWBR3TMTuAA9GIlZ/Jh2/5759v6oFDO0DAkKtpPaw8+Vez
/rHaTtHXuQZgXdiNlr8ap/QYKvkgFkOEHFUu46vv+CIpGBqQM4VK9c/AhFY7Fq+HQlUs
pLqWkMlJn1d7Piwe2nx5EGkRm6wEtd6xi7POMvKeqFxTd4t+fPIUE9U0MnkphA6s6oLx
SknA==
MIME-Version: 1.0
Received: by 10.14.184.133 with SMTP id s5mr1384709eem.31.1343249018560; Wed,
25 Jul 2012 13:43:38 -0700 (PDT)
Received: by 10.14.201.4 with HTTP; Wed, 25 Jul 2012 13:43:38 -0700 (PDT)
In-Reply-To: <20120725185343.GA6937@xxxxxxxxxxxxx>
References: <20120725185343.GA6937@xxxxxxxxxxxxx>
Date: Wed, 25 Jul 2012 16:43:38 -0400
Message-ID: <CAPBPrnugVm0RS5+Ljgg2E-AJygYsOSRjZW0Z=o9Mavs-SxTBog@xxxxxxxxxxxxxx>
Subject: Re: False positive from orphaned_commit_warning() ?
From: Dan Johnson <computerdruid@xxxxxxxxx>
To: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
Cc: git@xxxxxxxxxxxxxxx
Content-Type: text/plain; charset=UTF-8
Sender: git-owner@xxxxxxxxxxxxxxx
Precedence: bulk
List-ID: <git.vger.kernel.org>
X-Mailing-List: git@xxxxxxxxxxxxxxx
On Wed, Jul 25, 2012 at 2:53 PM, Paul Gortmaker
<paul.gortmaker@xxxxxxxxxxxxx> wrote:
> Has anyone else noticed false positives coming from the
> orphan check? It is warning me about commits that are
> clearly on master. Here is an example, where I checkout
> master~2 and then switch back to master. It somehow thinks
> that master~2 is orphaned, when master~2 is by definition
> in the commit chain leading to master.
I've been able to reproduce this with the following simplified recipe,
although I still don't know what is causing the failure (I'm not very
familiar with the code)
git init test
cd test
#make 3 commits
touch a && git add a && git commit -m a
touch b && git add b && git commit -m b
touch c && git add c && git commit -m c
#clone it
cd ..
git clone test test2
cd test2
git checkout master~2
git checkout master
#Warning: you are leaving 1 commit behind, not connected to
#any of your branches
I can't figure out what's going wrong here, but the clone is
important; it doesn't fail without it. It appears to have something to
do with the fact that the cloned repository has a remote, as:
#in test2
git remote rm origin
git checkout master~2
git checkout master
Does not throw the warning, but it's not just the presence of
origin/master that triggers it, as:
cd ../test
git remote add origin ../test2
git fetch origin
git checkout master~2
git checkout master
Does not trigger it either.
Confused,
--
-Dan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html