git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Matthias Lederhofer <matled@gmx.net>,
	git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH] git-status: colorize status output
Date: Mon, 7 Aug 2006 19:12:18 +0200	[thread overview]
Message-ID: <20060807171218.GB10918@mars.ravnborg.org> (raw)
In-Reply-To: <7v64h7e7dm.fsf@assigned-by-dhcp.cox.net>

> 
> Not that I can think of, but do people really run "git status"?
Always (almost) before I run 'git fetch'.
I do it to check that I have not made any local modifications that I
need to get rid of before fetching and that I do not have stale files
around.

One example is my copy of Linus' kernel tree. I use it now and then for
small experiments (can I reporoduce this bug etc) and when fetching I
want it to be gone.

	Sam

  parent reply	other threads:[~2006-08-07 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  3:14 [PATCH] git-status: colorize status output Jeff King
2006-08-05  3:21 ` Jeff King
2006-08-05  8:16   ` Greg KH
2006-08-05  9:28 ` Junio C Hamano
2006-08-05 10:21   ` Jeff King
2006-08-05 10:44     ` Jeff King
2006-08-05 10:59 ` Matthias Lederhofer
2006-08-05 11:21   ` Junio C Hamano
2006-08-05 11:27     ` Junio C Hamano
2006-08-05 11:28     ` Matthias Lederhofer
2006-08-05 11:42       ` Junio C Hamano
2006-08-05 12:18         ` Matthias Lederhofer
2006-08-05 19:54           ` Jeff King
2006-08-05 20:31             ` Matthias Lederhofer
2006-08-05 19:51         ` Jeff King
2006-08-07 17:12         ` Sam Ravnborg [this message]
2006-08-05 19:45   ` Jeff King
2006-08-05 20:27     ` Matthias Lederhofer
2006-08-05 23:42       ` Jeff King
2006-08-06  5:01 ` Joel Becker
2006-08-06  6:16   ` 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=20060807171218.GB10918@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=matled@gmx.net \
    --cc=peff@peff.net \
    /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).