From: Cristian Achim <brancoliticus@gmail.com>
To: git@vger.kernel.org
Subject: Usability outrage as far as I am concerned
Date: Wed, 20 Dec 2017 18:40:05 +0200 [thread overview]
Message-ID: <CAEW+b659_v02v8z_dgWzVayb8ArBOD+O_Oky-F50JbJSP8vCKQ@mail.gmail.com> (raw)
All I will do is paste the stackoverflow question below. It covers the
commands I made in chronological order and the way I would have
expected git to behave differently.
So I did
git pull home_subfolder
while in usb_subfolder. Can't remember the immediate output, but it
included a part about two repos having no commits in common. Would
have been wiser for git to just error out with a message that in one
of the folders there is not git repository.
At all times
git status
in home_subfolder gives
branch master
Working directory clean
This is so stupid considering the circumstances.
Doing again
git pull home_subfolder
at all times from usb_folder now returns U in front of 2 files in
home_folder and A in front of another file and then says
Pull is not possible because you have unmerged files
Had the bright idea to do
git clone home_subfolder
from the usb_subfolder because of my worries going away when
git status
in home_subfolder conforted me that there must be nothing bad about
the situation. Therefore I suspect that now doing
git pull usb_subfolder
from home_subfolder will do the same broken result as above.
I do not want to resolve merge conflicts because git doesn't error out
with a sane message of the situation when it should. I just want to
get the home_subfolder and usb_subfolder repositories state to where
it was before my breakage generating git pull and git clone commands.
Ubuntu 14.04 64 bit, git 1.9.1.
Thank you for your time.
next reply other threads:[~2017-12-20 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 16:40 Cristian Achim [this message]
2017-12-20 22:21 ` Usability outrage as far as I am concerned Ævar Arnfjörð Bjarmason
2017-12-21 2:29 ` Jacob Keller
2017-12-22 15:57 ` Cristian Achim
2017-12-22 23:05 ` Jacob Keller
2017-12-23 3:15 ` Anatolii Borodin
2017-12-23 12:22 ` Cristian Achim
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEW+b659_v02v8z_dgWzVayb8ArBOD+O_Oky-F50JbJSP8vCKQ@mail.gmail.com \
--to=brancoliticus@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).