git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: [EGIT RFC] Commit behaviour
Date: Fri, 13 Jun 2008 01:39:55 +0200	[thread overview]
Message-ID: <1213313997-1520-1-git-send-email-robin.rosenberg@dewire.com> (raw)


I got annoyed about having change my selection to a project to be able
to commit. This tentative feature allows me to hit the commit button
when any resource is selected and figure out which resources have been
modified. This makes it much easier to commit. Only the toolbar commit
is affected for now.

Another twist would be to list all changed resources, but only enable
the selected ones, or only the ones in in the same projects as the selected
resources. Comments?

Code is not efficient either. This is question about the user interface.

Then we could ask ourselved, should we do something similar for Checkout
and reset too? I think that is not as important as those operations are
much less frequent.

-- robin

             reply	other threads:[~2008-06-12 23:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 23:39 Robin Rosenberg [this message]
2008-06-12 23:39 ` [EGIT RFC] Add utilities for figuring out repositories for selected resources Robin Rosenberg
2008-06-12 23:39   ` [EGIT RFC] Enable commit for any resource in a Git-shared project Robin Rosenberg
2008-06-13 22:07 ` [EGIT RFC] Commit behaviour Marek Zawirski
2008-06-13 22:41   ` Marek Zawirski
2008-06-14  8:40     ` Robin Rosenberg
2008-06-14 10:05       ` Robin Rosenberg
2008-06-14  9:08   ` Robin Rosenberg
2008-06-14 10:23   ` Robin Rosenberg
2008-06-15  2:00     ` Marek Zawirski
2008-06-16  2:11 ` Shawn O. Pearce

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=1213313997-1520-1-git-send-email-robin.rosenberg@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).