git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steven Walter" <stevenrwalter@gmail.com>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: "Stephen R. van den Berg" <srb@cuci.nl>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-what: explain what to do next
Date: Tue, 27 May 2008 14:08:35 -0400	[thread overview]
Message-ID: <e06498070805271108t66a45abfy9abb5ed065e59e35@mail.gmail.com> (raw)
In-Reply-To: <8aa486160805270721q64dff3f0gfbb9eb5384db027d@mail.gmail.com>

On Tue, May 27, 2008 at 10:21 AM, Santi Béjar <sbejar@gmail.com> wrote:
> On Tue, May 27, 2008 at 3:52 PM, Stephen R. van den Berg <srb@cuci.nl> wrote:
>> Santi B?jar wrote:
>>>On Tue, May 27, 2008 at 3:12 PM, Johannes Schindelin
>>><Johannes.Schindelin@gmx.de> wrote:
>>>> Sure it is.  But cluttering up the commands for something that is not
>>>> really proven to be wanted by many is IMO inferior.

WANT.

>>>This is an argument against git-whatzzup.sh in general. Point taken.
>>
>> Not really.  It's an argument against cluttering up the existing core
>> with this stuff.

The only changes I saw were to porcelain, not plumbing (or is this not
what you mean by "core?")  I see no problem with making the plumbing
more user-friendly.  That is really the only point of the porcelain.
If you don't want user-friendly, use the plumbing directly.

> It is not a hands-on tutorial, it is more of "in which state (merging,
> bisecting,...) is my working tree, if it is in the middle of a complex
> process (bisect, merge, rebase,...) tell me what was the help
> message". It is not that different from the output of "git status",
> but for states.

Surely it has happened to everyone that you start a rebase, walk away
and then continue hacking and committing with the rebase still in
progress.  It isn't too bad for an experienced user to recover from
this state, but prevention is much better than cure.  A simple "git
what" command that could remind you of what you were doing would be a
welcome addition, in my mind.
-- 
-Steven Walter <stevenrwalter@gmail.com>
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects."
 -Robert Heinlein

  reply	other threads:[~2008-05-27 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  8:34 [RFC/PATCH] git-what: explain what to do next Santi Béjar
2008-05-27 10:53 ` Johannes Schindelin
2008-05-27 12:58   ` Santi Béjar
2008-05-27 13:12     ` Johannes Schindelin
2008-05-27 13:37       ` Santi Béjar
2008-05-27 13:52         ` Stephen R. van den Berg
2008-05-27 14:21           ` Santi Béjar
2008-05-27 18:08             ` Steven Walter [this message]
2008-05-27 20:24               ` Junio C Hamano
2008-05-27 20:51       ` Junio C Hamano
2008-05-28  9:12         ` Santi Béjar
2008-05-29  4:39 ` Christian Couder
2008-05-29  5:09   ` Junio C Hamano
2008-05-29 14:56     ` Jon Loeliger

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=e06498070805271108t66a45abfy9abb5ed065e59e35@mail.gmail.com \
    --to=stevenrwalter@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sbejar@gmail.com \
    --cc=srb@cuci.nl \
    /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).