Discussion:
remotename extension: abort: push would create new anonymous heads
Uwe Brauer
2018-10-11 15:13:52 UTC
Permalink
Hi

This extensions drives my crazy. I just created a dummy repo in
bitbucket, called test, then I do

echo "First" > test.org
hg add test.org
hg commit -m "First"
echo "Second" >> test.org
hg commit -m "Second"
hg branch feature
echo "Third" >> test.org
hg commit -m "Third"

And I push,
(my path is
[paths]
bitbucket = https://***@bitbucket.org/kalthad/test)


hg push bitbucket


I obtain

pushing to https://***@bitbucket.org/kalthad/test
searching for changes
abort: push would create new anonymous heads (d20f51babeaf, f58f50b9f784)
(use --allow-anon to override this warning)

That does not look appealing.

I did it anyway and I obtain

hg log -G


@ changeset: 2:d334742cb030
| branch: feature
| tag: tip
| branch: bitbucket/feature
| user: Uwe Brauer <***@mat.ucm.es>
| date: Thu Oct 11 17:11:40 2018 +0200
| summary: Third
|
o changeset: 1:3b9813a5763e
| branch: bitbucket/default
| user: Uwe Brauer <***@mat.ucm.es>
| date: Thu Oct 11 17:11:40 2018 +0200
| summary: Second
|
o changeset: 0:0cc11a43813f
user: Uwe Brauer <***@mat.ucm.es>
date: Thu Oct 11 17:11:39 2018 +0200
summary: First


So far so good, but why on earth the --allow-anon message.
How can I avoid this message?


I am puzzled.

Uwe Brauer

Loading...