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

Re: [EGIT RFC] Commit behaviour

From
MZMarek Zawirski <marek.zawirski@gmail.com>
Date
Jun 13, 2008, 22:41 UTC
Message-ID
<4852F79D.4080100@gmail.com>
In-Reply-To
<4852EFBF.6000406@gmail.com>
> Robin Rosenberg wrote:
>> 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.

Hey, by the way - do we already have some action for checkout? Did I missed something?

-- 
Marek Zawirski [zawir]
marek.zawirski@gmail.com
Previous: Marek ZawirskiNext: Robin Rosenberg
Message 5 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.