From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh Users <zsh-users@zsh.org>
Subject: git adventures
Date: Fri, 14 Nov 2014 09:39:30 -0800 [thread overview]
Message-ID: <54663E52.9040406@eastlink.ca> (raw)
Gitmeisters:
(CAPS NOT YELLING ;-)
pts/0 HP-y5--5-Debian1 root /aMisc/zsh-code $ git pull --rebase
Cannot pull with rebase: You have unstaged changes.
Please commit or stash them.
pts/0 HP-y5--5-Debian1 root /aMisc/zsh-code $ git pull
remote: Counting objects: 41, done.
remote: Compressing objects: 100% (29/29), done.
remote: Total 29 (delta 23), reused 0 (delta 0)
Unpacking objects: 100% (29/29), done.
From git://git.code.sf.net/p/zsh/code
e334119..8505837 master -> origin/master
Updating e334119..8505837
error: Your local changes to the following files would be
overwritten by merge:
THIS IS JUST TO FIX THAT PROBLEM I HAD WITH 'make check'. COOL THAT
GIT KNOWS THAT, AND WON'T OVERWRITE IT.
Test/B06fc.ztst
Please, commit your changes or stash them before you can merge.
Aborting
pts/0 HP-y5--5-Debian1 root /aMisc/zsh-code $ git pull origin master
From git://git.code.sf.net/p/zsh/code
* branch master -> FETCH_HEAD
Updating e334119..8505837
error: Your local changes to the following files would be
overwritten by merge:
Test/B06fc.ztst
Please, commit your changes or stash them before you can merge.
Aborting
I'VE LEARNED ABOUT 'stage', BUT WHAT IS 'stash'?
HOW DO I commit/stash/stage THAT ONE FILE SO AS TO PROCEED? CAN WE TELL GIT
TO JUST NOT WORRY ABOUT THAT FILE--LEAVE IT BE, BUT PULL EVERYTHING ELSE?
THAT CHANGED FILE IS OBVIOUSLY ONLY OF TEMPORARY VALUE.
FANTASTIC DOC:
http://git-scm.com/book/en/v2
I'M LIKING AND RESPECTING GIT ALREADY. MOST COOL THAT IT CLONES IT'S OWN
ADMINISTRATION HERE AS WELL AS FILES, ALSO THAT IT REMEMBERS WHERE THE
MOTHER SHIP IS. GENUINELY HELPFUL ERROR MESSAGES! HOW UN-LINUX.
next reply other threads:[~2014-11-14 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 17:39 Ray Andrews [this message]
2014-11-14 16:46 ` Nathan Schwarz
2014-11-14 16:51 ` Nathan Schwarz
2014-11-14 19:55 ` Ray Andrews
2014-11-14 23:40 ` Bart Schaefer
2014-11-15 0:17 ` Nathan Schwarz
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=54663E52.9040406@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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).