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

Re: StGIT: "stg new" vs "stg new --force"

From
CMCatalin Marinas <catalin.marinas@gmail.com>
Date
Jan 16, 2006, 08:18 UTC
Message-ID
<b0943d9e0601160018x206faf9ck@mail.gmail.com>
In-Reply-To
<1137144291.20073.104.camel@dv>
Hi Pavel,
On 13/01/06, Pavel Roskin <proski@gnu.org> wrote:
> Maybe I don't understand something in StGIT, but it seems strange that
> "stg new" creates empty patch by default and requires "--force" to
> create a non-empty patch.

The 'new' command would fail to create a new patch if there are changes in the tree.

I also find myself using the '--force' option most of the time. Even when I create a an empty patch, I use to run 'status' before. The current implementation is closer to Quilt where, AFAIK, you first create a new patch and use 'add' for every modified file. Since 'add' has a different meaning in StGIT, it might also make sense to remove the '--force' option.

Show 6 quoted lines
> 1) "stg new --force" becomes "stg new" and "stg new" becomes "stg new
> --empty", i.e. empty files can only be created with the "--empty"
> switch.
> 2) "stg new --force" becomes "stg record" or something.
> 3) "stg new --force" becomes "stg new --record" or something.
> 4) "stg new" works both with and without modified files.

Regarding (1), the newly created patch is empty anyway, you would need to run 'refresh' to add the modified patches to it ('stg series -e' would show the empty patches prefixed with a 0).

Anyway, I would also prefer option 4. If there are no objections, I'll modify StGIT accordingly. It would also be useful to have a wiki page about StGIT vs. Quilt to show the main differences.

-- Catalin

Previous: Karl HasselströmNext: Pavel Roskin
Message 3 of 19 in “StGIT: "stg new" vs "stg new --force"”
  1. Pavel RoskinJan 13, 2006
  2. Karl HasselströmJan 13, 2006
  3. Catalin MarinasJan 16, 2006
  4. Pavel RoskinJan 17, 2006
  5. Yann DirsonJan 17, 2006
  6. Pavel RoskinJan 17, 2006
  7. Yann DirsonJan 18, 2006
  8. Pavel RoskinJan 19, 2006
  9. Yann DirsonJan 19, 2006
  10. Pavel RoskinJan 20, 2006
  11. J. Bruce FieldsJan 20, 2006
  12. Pavel RoskinJan 24, 2006
  13. J. Bruce FieldsJan 24, 2006
  14. Pavel RoskinJan 24, 2006
  15. Catalin MarinasJan 24, 2006
  16. Catalin MarinasJan 21, 2006
  17. Pavel RoskinJan 22, 2006
  18. Catalin MarinasJan 21, 2006
  19. Catalin MarinasJan 21, 2006

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.