git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [EGIT RFC] Commit behaviour

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jun 16, 2008, 02:11 UTC
Message-ID
<20080616021158.GQ11793@spearce.org>
In-Reply-To
<1213313997-1520-1-git-send-email-robin.rosenberg@dewire.com>
Robin Rosenberg <robin.rosenberg@dewire.com> wrote:
Show 9 quoted lines
> 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?

I think this is a good idea. You really do want to make commits that cover the entire repository, rather than a subsection of it. I think that covering the whole repository is much more common.

> 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.

Yes, we do want to. If you are doing a reset you probably need to whack everything that is dirty and restore the state, likewise if you are doing a checkout you are likely switching branches and would expect the entire repository to switch at once.

-- 
Shawn.
Previous: Marek Zawirski
Message 11 of 11 in “[EGIT RFC] Commit behaviour”
  1. Robin RosenbergJun 12, 2008
  2. [EGIT RFC] Add utilities for figuring out repositories for selected resourcesRobin Rosenberg, Jun 12, 2008
  3. [EGIT RFC] Enable commit for any resource in a Git-shared projectRobin Rosenberg, Jun 12, 2008
  4. Marek ZawirskiJun 13, 2008
  5. Marek ZawirskiJun 13, 2008
  6. Robin RosenbergJun 14, 2008
  7. Robin RosenbergJun 14, 2008
  8. Robin RosenbergJun 14, 2008
  9. Robin RosenbergJun 14, 2008
  10. Marek ZawirskiJun 15, 2008
  11. Shawn O. PearceJun 16, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.