From: Jakub Narebski <jnareb@gmail.com>
To: Yann Dirson <ydirson@altern.org>
Cc: git@vger.kernel.org
Subject: Re: Rebasing stgit stacks
Date: Fri, 19 Jan 2007 10:40:16 +0100 [thread overview]
Message-ID: <200701191040.17476.jnareb@gmail.com> (raw)
In-Reply-To: <20070117205301.GH9761@nan92-1-81-57-214-146.fbx.proxad.net>
On Wed, Jan 17, 2007 Yann Dirson wrote:
> On Wed, Jan 17, 2007 at 12:30:18AM +0100, Jakub Narebski wrote:
>> I'm all for calling this command "stg rebase".
>
> After all, my current implementation as "pull --to" mostly bypasses
> the fetch, so it probably makes sense to use a new command.
>
> However, "stg rebase <target>" does not sound right. I'm not very
> happy with "stg rebaseto <target>" (or rebase-to) either.
> "stg rebase --to <target>" may feel strange too (command without
> non-option arg), but may finally a good choice after all ? What do
> others think ?
First, "stg rebase" when on some git branch might mean rebase StGIT
stack to head of current branch (because there were some git commits
on top of this branch). So it would be "stg rebase [--onto <target>]";
it would be command without non-option arg, but this arg would be
optional.
Second, if you were to implement separating commands into subcommands
(perhaps just as alternative names) depending on what they act on:
"stg stack <subcommand>", "stg patch <subcommand>" etc., this would
I think belong to "stg base <subcommand>".
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-01-19 9:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 21:35 Howto use StGit and git-svn at same time Guilhem Bonnefille
2007-01-09 21:41 ` Guilhem Bonnefille
2007-01-09 22:41 ` Yann Dirson
2007-01-15 13:26 ` Guilhem Bonnefille
2007-01-15 20:24 ` Rebasing stgit stacks Yann Dirson
2007-01-15 22:46 ` Catalin Marinas
2007-01-15 23:39 ` Yann Dirson
2007-01-16 22:42 ` Catalin Marinas
2007-01-16 23:17 ` Yann Dirson
2007-01-16 23:30 ` Jakub Narebski
2007-01-17 9:03 ` Karl Hasselström
2007-01-17 11:07 ` David Kågedal
2007-01-17 19:34 ` Yann Dirson
2007-01-17 20:53 ` Yann Dirson
2007-01-18 12:06 ` Catalin Marinas
2007-01-18 19:42 ` Yann Dirson
2007-01-19 9:40 ` Jakub Narebski [this message]
2007-01-20 13:17 ` Yann Dirson
2007-01-20 19:16 ` Jakub Narebski
2007-01-20 20:07 ` Yann Dirson
2007-01-22 23:12 ` Catalin Marinas
2007-01-18 9:05 ` Catalin Marinas
2007-01-18 20:52 ` Yann Dirson
2007-01-19 9:47 ` Jakub Narebski
2007-01-22 17:54 ` Catalin Marinas
2007-01-22 19:47 ` Yann Dirson
2007-01-22 22:58 ` Catalin Marinas
2007-01-23 7:49 ` Yann Dirson
2007-01-23 22:03 ` Catalin Marinas
2007-01-24 0:05 ` Yann Dirson
2007-01-24 12:37 ` Catalin Marinas
2007-01-24 20:03 ` Yann Dirson
2007-01-28 4:33 ` Theodore Tso
2007-01-28 10:25 ` Yann Dirson
2007-01-28 23:21 ` Catalin Marinas
2007-01-17 21:30 ` Yann Dirson
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=200701191040.17476.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=ydirson@altern.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.