From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Wincent Colaiuta <win@wincent.com>
Cc: git@vger.kernel.org
Subject: Re: I want "fast forward my workdir to upstream if it's safe"
Date: Thu, 07 May 2009 16:20:22 -0700 [thread overview]
Message-ID: <86ljp8fqkp.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <FC9BF880-D69F-4A56-B9FA-EF5BDBF73437@wincent.com> (Wincent Colaiuta's message of "Fri, 8 May 2009 01:18:32 +0200")
>>>>> "Wincent" == Wincent Colaiuta <win@wincent.com> writes:
>> I want a *command* I can tell people in #git.
Wincent> "git status"?
Wincent> # On branch master
Wincent> # Your branch is ahead of 'origin/master' by 46 commits.
Wincent> #
Wincent> # Changed but not updated:
Wincent> # (use "git add <file>..." to update what will be committed)
Wincent> # (use "git checkout -- <file>..." to discard changes in working directory)
Wincent> #
Wincent> # modified: foo
Wincent> #
Wincent> # Untracked files:
Wincent> # (use "git add <file>..." to include in what will be committed)
Wincent> #
Wincent> # bar
Now, you expect them to parse that in a script? "git status" is porcelain,
not plumbing, and can change from version to version, and has.
I want a command I can put in a cron job that Does The Right Thing.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
next prev parent reply other threads:[~2009-05-07 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 21:40 I want "fast forward my workdir to upstream if it's safe" Randal L. Schwartz
2009-05-07 23:18 ` Wincent Colaiuta
2009-05-07 23:20 ` Randal L. Schwartz [this message]
2009-05-08 2:30 ` Jeff King
2009-05-08 6:53 ` Andreas Ericsson
2009-05-08 7:01 ` Jeff King
2009-05-08 12:34 ` Eyvind Bernhardsen
2009-05-08 14:02 ` Randal L. Schwartz
2009-05-08 15:57 ` Junio C Hamano
2009-05-08 16:15 ` Jakub Narebski
2009-05-11 20:11 ` Eyvind Bernhardsen
2009-05-08 21:34 ` Miles Bader
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=86ljp8fqkp.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.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 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).