From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org, walt <wa1ter@myrealbox.com>
Subject: Re: My first git success [not quite]
Date: Sat, 14 Jan 2006 12:31:18 -0800 [thread overview]
Message-ID: <7vzmlyft61.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86acdyu2dz.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "14 Jan 2006 09:48:24 -0800")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> Well, I'm a developer and *I* also had that problem while working
> on my "ajax" branch.
>
> Maybe git-checkout should by default *warn* when it is leaving
> things in the tree that are indexed but not updated in the index...
What Linus already said. But you may find this on top of the
current "master" branch useful.
Likes, dislikes?
-- >8 --
[PATCH] checkout: show dirty state upon switching branches.
This shows your working file state when you switch branches. As
a side effect, "git checkout" without any branch name (i.e. stay
on the current branch) becomes a more concise shorthand for the
"git status" command.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
diff --git a/git-checkout.sh b/git-checkout.sh
index bd7f007..d99688f 100755
--- a/git-checkout.sh
+++ b/git-checkout.sh
@@ -164,6 +164,9 @@ else
esac
exit 0
)
+ saved_err=$?
+ git diff-files --name-status
+ (exit $saved_err)
fi
#
next prev parent reply other threads:[~2006-01-14 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 14:51 My first git success walt
2006-01-13 17:11 ` Linus Torvalds
2006-01-13 18:57 ` Randal L. Schwartz
2006-01-13 19:37 ` Junio C Hamano
2006-01-13 20:14 ` Peter Eriksen
2006-01-14 15:39 ` My first git success [not quite] walt
2006-01-14 15:55 ` sean
2006-01-14 15:55 ` sean
2006-01-14 17:18 ` walt
2006-01-14 17:48 ` Randal L. Schwartz
2006-01-14 20:31 ` Junio C Hamano [this message]
2006-01-14 19:25 ` Linus Torvalds
2006-01-14 20:41 ` walt
2006-01-14 20:49 ` Junio C Hamano
2006-01-14 21:57 ` Linus Torvalds
2006-01-15 10:44 ` Junio C Hamano
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=7vzmlyft61.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=wa1ter@myrealbox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.