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

Re: StGIT: "stg refresh -e/--edit" to refresh patch and edit description no longer works

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 14, 2007, 16:01 UTC
Message-ID
<200712141701.43914.jnareb@gmail.com>
In-Reply-To
<b0943d9e0712140626w3a2f55b1i83c33f93d7f8af2f@mail.gmail.com>
On Fri, 14 Dec 2007, Catalin Marinas wrote:
Show 14 quoted lines
> On 14/12/2007, Jakub Narebski <jnareb@gmail.com> wrote:
>>
>> The command I used quite often in my StGIT workflow, namely
>> "stg refresh -e", which used to refresh patch and launch editor to edit
>> commit (patch) description no longer works in Stacked GIT 0.14.1.
>>
>> I used it when new (refreshed) changes needed also changes in commit
>> description (commit message). Now I have to run two commands:
>> "stg refresh" and "stg edit".
> 
> Well, people complained that 'refresh -e' is misleading and a separate
> command is needed. It's not difficult to move the editing
> functionality out of stgit.commands.edit and re-add the --edit option
> to refresh (while also keeping the separate edit command).

First, the "misleading" part could be corrected by renaming long option to --edit-description or --edit-message. Second "stg refresh -e" matches non-StGIT usage of "git commit --amend"; and it is damn useful to have it as one command, not two.

> I'm a bit busy with home/family commitments until the new year.

I'll wait. As I am not running StGIT master, but released version, I would have to waith nevertheless on next release.

TIA
-- 
Jakub Narebski
Poland
Previous: Catalin Marinas
Message 3 of 3 in “StGIT: "stg refresh -e/--edit" to refresh patch and edit description no longer works”
  1. Jakub NarebskiDec 14, 2007
  2. Catalin MarinasDec 14, 2007
  3. Jakub NarebskiDec 14, 2007

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.