-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency of the capitalization: Default vs default #3
Comments
Hello. I do not fully understand your question. Do you want to push to GitHub but failed? I guess you mentioned me because of this. Unfortunately I did not keep on with it. I encountered a problem (cannot recall what it is, maybe something about branch) and did not find solution. Everything I know about how to use TortoiseHg with GitHub is written in that repo. I know nothing more. If TortoiseHg is giving you trouble pushing to GitHub, you may consider switching to Git. Yeah, not pleasing for Hg fans I know... |
I haven't used a github from TortoiseHg for a long time. Therefore, I will give only a few recommendations for hg-git.
|
Hi Kotsuha, Generated by TortoiseHg settings dialog[tortoisehg] [mq] [phases] [ui] Sincerely, |
Hi vitidev, This new effort may take some time. Pertaining to this issue, I prefer the capitalized Default for use by the github.com server consistently, because the lower-case default seems to have a restricted meaning in at least the TortoiseHg client. |
hg-git won't be able to properly push the existing hg repository (to empty github repo) if it contains branches. |
Following @torbjoernk (2013), I'll try to avoid using mercurial subrepositories = "branches." |
I think I'll attempt to do the grunt work for my 70 files: I have tried cloning, but TortoiseHg gives the message that it does not appear to be an hg repository. |
This means that the hg-git extenison is not enabled |
Can someone please help me ?
I am a new person, having pushed from a TortoiseHg 5.7 client.
Thank you,
dloksnel@gmail.com
@Kotsuha
@10063987
@vitidev
@owenvoke
@sebunger
@philpep
@frescobaldi
The text was updated successfully, but these errors were encountered: