From: Aghiles <aghilesk@gmail.com>
To: git list <git@vger.kernel.org>
Subject: git pull with "no common commits" : danger?
Date: Wed, 7 Apr 2010 21:56:56 -0400 [thread overview]
Message-ID: <v2t3abd05a91004071856s5811e086q17241996a359e172@mail.gmail.com> (raw)
Hello,
I mistakenly pulled a project into another project. I had the
"warning: no common commits" but the pull did proceed.
I am wondering if, from a usability point of view, it would be
best to avoid doing so by default.
Thanks,
-- aghiles
next reply other threads:[~2010-04-08 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 1:56 Aghiles [this message]
2010-04-08 2:08 ` git pull with "no common commits" : danger? Michael J Gruber
2010-04-08 2:43 ` Aghiles
2010-04-08 5:44 ` Jonathan Nieder
2010-04-08 19:55 ` Aghiles
2010-04-08 6:20 ` Junio C Hamano
2010-04-08 19:46 ` Aghiles
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=v2t3abd05a91004071856s5811e086q17241996a359e172@mail.gmail.com \
--to=aghilesk@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).