All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
	Daniel Thomas <drt24@srcf.ucam.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: the careless committer and fear of commitment (rebase -i vs add  -p)
Date: Tue, 30 Mar 2010 11:44:01 +0530	[thread overview]
Message-ID: <f3271551003292314v23058945vb432cc4c8a601aca@mail.gmail.com> (raw)
In-Reply-To: <20100330045704.GA9004@progeny.tock>

Hi,

On Tue, Mar 30, 2010 at 10:32 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> I like ‘git diff --cached’ and ‘git diff’ to show the entire list
> of staged and unstaged changes.  I don’t consider this “wrong” at all.

On a related note, my workflow is somewhat similar: I just use Magit
within Emacs, which essentially does the same thing. The staging area
in Git really helps me organize my work, and I wouldn't mind attaching
a small note to it that I can refer to while writing my commit message
(much like Jonathan's idea). However, I don't think this task is large
enough for an entire GSoC.

Also, I'm positively opposed to the idea of a complex interactive
command-line interface. If someone *did* want that kind of complexity/
interactivity, they ought to use something like Magit: a cli can't
even come close.

-- Ram

  reply	other threads:[~2010-03-30  6:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 19:32 [GSoC Proposal/RFC] Rolling commit message writing Daniel Thomas
2010-03-29 20:31 ` Avery Pennarun
2010-03-30  3:05   ` Jonathan Nieder
2010-03-30  4:32     ` Avery Pennarun
2010-03-30  5:02       ` the careless committer and fear of commitment (rebase -i vs add -p) Jonathan Nieder
2010-03-30  6:14         ` Ramkumar Ramachandra [this message]
2010-03-30 17:27   ` [GSoC Proposal/RFC] Rolling commit message writing 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=f3271551003292314v23058945vb432cc4c8a601aca@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=drt24@srcf.ucam.org \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@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.