From: Miklos Vajna <vmiklos@frugalware.org>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Johannes Sixt <johannes.sixt@telecom.at>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] checkout without arguments does not make sense
Date: Mon, 21 Jul 2008 23:44:59 +0200 [thread overview]
Message-ID: <20080721214459.GJ32057@genesis.frugalware.org> (raw)
In-Reply-To: <32541b130807211436h77bf5985xa61ed7b4941c47dc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Mon, Jul 21, 2008 at 05:36:59PM -0400, Avery Pennarun <apenwarr@gmail.com> wrote:
> Eek, are we using "checkout" to get status information now? If that
> goes wrong, you could be blowing away your locally modified data by
> accident.
Hm, let's say I have uncommitted changes to Makefile, then I'll get:
$ git checkout
M Makefile
Your branch is ahead of the tracked remote branch 'junio/next' by 1 commit.
But it will not drop my local changes.
> I think "git status" reports this information in recent versions, doesn't it?
Right. But that shows other infos as well, for example the untracked
files, etc. So there are cases when git checkout is just better.
However, you are right about it may not be the best habit from my side
to use git checkout to get that info. ;-)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-21 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 20:06 [PATCH] checkout without arguments does not make sense Johannes Sixt
2008-07-21 20:49 ` Miklos Vajna
2008-07-21 21:11 ` Johannes Sixt
2008-07-21 21:36 ` Avery Pennarun
2008-07-21 21:44 ` Miklos Vajna [this message]
2008-07-22 0:57 ` Johannes Schindelin
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=20080721214459.GJ32057@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
/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).