emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@Nexgo.DE>
To: emacs-orgmode@gnu.org
Subject: Re: Proper git settings to stay with master?
Date: Sat, 24 Dec 2016 12:15:01 +0100	[thread overview]
Message-ID: <o3llbi$5eq$1@blaine.gmane.org> (raw)
In-Reply-To: <CA+M2ft8JAAk+fM30yOdzFB0GbLzPsLuTioLshQS89HmnbGy-jg@mail.gmail.com>

Am 23.12.2016 um 20:49 schrieb John Hendy:
> Sure... I get that that I *can* do that. I just wondered why I
> *needed* to do that.

When you are in a "detached HEAD" situation, you will always have to 
tell git explicitly to switch to some other commit (most likely a 
branch).  Git pull works with branch heads, but you've not checked out 
any, so it won't do anything and can't, since it will potentially lose 
data if it tried.

> This makes sense. I don't know why this never happened before, but
> checking out a specific commit makes sense.

Checking out a specific commit not at the branch head, to be precise.

 > Perhaps I was bisecting
> something in the past and checking out various commits? Once you check
> out *something*, do you always have to re-checkout something else to
> undo this effect (and make it like the default)? As in if I check out
> a commit and then =git pull=, it won't go back to master?

Git status tells you where you've currently checked out.


-- 
Achim.

(on the road :-)

      reply	other threads:[~2016-12-24 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 16:44 Proper git settings to stay with master? John Hendy
2016-12-23 11:24 ` Achim Gratz
2016-12-23 19:49   ` John Hendy
2016-12-24 11:15     ` Achim Gratz [this message]

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: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='o3llbi$5eq$1@blaine.gmane.org' \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).