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

Re: [StGit PATCH] Allow renaming of the top-most branch by just calling stg rename <new-patch-name>

From
Karl Hasselström <kha@treskal.com>
Date
Feb 18, 2008, 14:00 UTC
Message-ID
<20080218140005.GA18668@diana.vm.bytemark.co.uk>
In-Reply-To
<200802172203.55533.onno@gmx.net>
This is a good idea, I think.
On 2008-02-17 22:03:55 +0100, Onno Kortmann wrote:
> instead of stg rename <old> <new>. This is for example helpful for
> those people who always have a typo or two in their patch names.

Please follow the commit message conventions. That is, first one short summary line, then a blank line and the rest of the commit message. And a sign-off.

(Read git's Documentation/SubmittingPatches if you want the details.)
> +        args=[crt]+args
> +        out.start('Renaming top-most patch "%s" to "%s"' % (args[0], 
> args[1]))

Please consider storing the patch names in two suitably named variables, like this:

  if len(args) == 1:
     old, [new] = crt, args
  elif len(args) == 2:
     old, new = args
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Onno KortmannNext: Onno Kortmann
Message 2 of 10 in “Allow renaming of the top-most branch by just calling stg rename <new-patch-name>”
  1. Allow renaming of the top-most branch by just calling stg rename <new-patch-name>Onno Kortmann, Feb 17, 2008
  2. Karl HasselströmFeb 18, 2008
  3. Onno KortmannFeb 21, 2008
  4. Karl HasselströmFeb 22, 2008
  5. Onno KortmannFeb 22, 2008
  6. Karl HasselströmFeb 23, 2008
  7. 1/2 Simple rename of top-most patchOnno Kortmann, Feb 21, 2008
  8. Karl HasselströmFeb 22, 2008
  9. 2/2 Test the 'stg rename' commandOnno Kortmann, Feb 21, 2008
  10. Karl HasselströmFeb 22, 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.