All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH] rebase: learn --discard subcommand
Date: Sun, 29 May 2011 06:41:44 -0700 (PDT)	[thread overview]
Message-ID: <m3r57hy68n.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1105290850340.28815@debian>

Martin von Zweigbergk <martin.von.zweigbergk@gmail.com> writes:

> Maybe the recent patch [1] about adding information to git status
> about any ongoing operation would help. I'm not sure, but I think I
> would personally be a bit hesitant to cancel the current sequence
> operation without first checking what it was. OTOH, if I don't even
> remember starting a rebase operation, maybe knowing whether it was a
> rebase or an am operation might not help much. But if the message from
> git status would actually say something like "rebase in progress:
> [2/3] War on nbsp: a bit of retreat", then that might help more in
> making a decision to cancel or not.
> 
>  [1] http://thread.gmane.org/gmane.comp.version-control.git/172919

Such information could be not enough.  I understand that "git status"
output space is limited, but it would be nice if e.g. "git status -v"
described current state in more detail:

  rebase in progress: [2/3] War on nbsp: a bit of retreat"
  rebasing xx/foo --onto master~5

It would describe which branch were we rebasing, and on what commit
(preferring for name-rev description to start from branch we were
rebasing onto, if possible).

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2011-05-29 13:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28  2:58 [PATCH] rebase: learn --discard subcommand Martin von Zweigbergk
2011-05-28 13:15 ` Ramkumar Ramachandra
2011-05-29 12:50   ` Martin von Zweigbergk
2011-05-28 18:51 ` Junio C Hamano
2011-05-28 20:26   ` Tim Mazid
2011-05-28 22:50     ` Jonathan Nieder
2011-05-29 13:14   ` Martin von Zweigbergk
2011-05-29 13:41     ` Jakub Narebski [this message]
2011-05-30  4:50   ` Michael Haggerty
2011-05-28 23:08 ` Jonathan Nieder
2011-05-29  9:30   ` Tim Mazid
2011-05-29 17:28   ` Martin von Zweigbergk
2011-05-29 18:58     ` Jonathan Nieder
2011-05-30  4:46   ` Michael Haggerty
2011-05-30  5:14     ` Tim Mazid
2011-05-30  8:44       ` Michael Haggerty
2011-05-30  5:01   ` 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=m3r57hy68n.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.von.zweigbergk@gmail.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.