From: Adam Megacz <adam@megacz.com>
To: git@vger.kernel.org
Subject: "warning: Updating the currently checked out branch may cause confusion" on bare repositories
Date: Mon, 18 Jan 2010 22:41:26 +0000 [thread overview]
Message-ID: <xuu2ska3doix.fsf@nowhere.com> (raw)
It seems that the message "warning: Updating the currently checked out
branch may cause confusion" is unnecessary when pushing to a bare
"myproject.git" repository (instead of a "myproject/.git" repository).
Is this the case?
If so, perhaps the warning should be omitted when the target is a bare
repository.
- a
next reply other threads:[~2010-01-18 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:41 Adam Megacz [this message]
2010-01-19 6:29 ` "warning: Updating the currently checked out branch may cause confusion" on bare repositories Shawn O. Pearce
2010-01-19 18:55 ` Adam Megacz
2010-01-19 18:59 ` Shawn O. Pearce
2010-01-19 22:43 ` Jeff King
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=xuu2ska3doix.fsf@nowhere.com \
--to=adam@megacz.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).