From: Onno Kortmann <onno@gmx.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH] Allow renaming of the top-most branch by just calling stg rename <new-patch-name>
Date: Thu, 21 Feb 2008 22:30:56 +0100 [thread overview]
Message-ID: <200802212230.56646.onno@gmx.net> (raw)
In-Reply-To: <20080218140005.GA18668@diana.vm.bytemark.co.uk>
Hi,
> > 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.
Ok, I tried to do this, I'm not used at all to sending patches with (st)git :-)
Thanks for the pointer and the assistance. Hopefully, --refid works as I
understand it and the new patches appear in this thread.
> Please consider storing the patch names in two suitably named
> variables, like this:
I fixed that one, too.
I'll send out another patch, a test case for the stg rename command.
Greetings,
Onno
next prev parent reply other threads:[~2008-02-21 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 21:03 [StGit PATCH] Allow renaming of the top-most branch by just calling stg rename <new-patch-name> Onno Kortmann
2008-02-18 14:00 ` Karl Hasselström
2008-02-21 21:30 ` Onno Kortmann [this message]
2008-02-22 7:38 ` Karl Hasselström
2008-02-22 22:52 ` Onno Kortmann
2008-02-23 7:45 ` Karl Hasselström
2008-02-21 21:42 ` [PATCH 1/2] Simple rename of top-most patch Onno Kortmann
2008-02-22 7:44 ` Karl Hasselström
2008-02-21 21:43 ` [PATCH 2/2] Test the 'stg rename' command Onno Kortmann
2008-02-22 7:48 ` Karl Hasselström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802212230.56646.onno@gmx.net \
--to=onno@gmx.net \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).