From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: "GIT list" <git@vger.kernel.org>
Subject: Re: [PATCH] Add contrib/stg-gitk: helper script to run gitk
Date: Fri, 12 Jan 2007 23:09:22 +0000 [thread overview]
Message-ID: <b0943d9e0701121509t6d3ca059v9b7389ff3242c06b@mail.gmail.com> (raw)
In-Reply-To: <20070112224733.GA9761@nan92-1-81-57-214-146.fbx.proxad.net>
On 12/01/07, Yann Dirson <ydirson@altern.org> wrote:
> Indeed "stg series -g" may differ too much from "stg-gitk" to plug the
> functionnality at this place: "stg series" is a command acting on one
> stack, whereas stg-gitk is a repository-wide command, allowing to draw
> several stacks, and also includes anything below stack base, which
> looks also out of the scope of "stg series -g". Maybe a new command
> is called for - possibly as something like
> "stg repo graph [<branch>...]" ?
Maybe repo --graph at the moment (until we add some unified support
for subcommands) but not sure what other options would go into 'repo'.
Anyway, I haven't had time to try any of your scripts yet and I don't
know what stg-gitk shows.
> OK, the command names were borrowed from tools which provide a
> fraction of the functionnality stgit (not exactly so in the case of
> GIT, OK ;). That makes it easy for people used to those commands that
> served as inspiration to the stgit ones, I know that (I used quilt
> before stgit). But I do feel that having a more consistent command
> set would help - remember quilt has no idea of branches, multiple
> repositories and history, stgit is in many ways a very different beast :)
StGIT probably got enough advertisement as being a Quilt replacement
for GIT. It would be OK to re-organize the commands (and use aliases
to still have the current functionality).
As I said in a different e-mail, I'd first like to get StGIT in a
feature-freeze state (well, mainly not changing major things) and fix
the remaining bugs to get 1.0 out. After that, we can redefine the
commands, repository structure or whatever has a bad design.
> There are already aliases in GIT itself, they are quite simple to
> understand, and would probably require very little code in python.
> I'll have a look at that, unless you would veto integration of such a
> patch.
I'd like this patch (though I haven't used aliases in GIT yet).
--
Catalin
prev parent reply other threads:[~2007-01-12 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 22:12 [PATCH] Add contrib/stg-gitk: helper script to run gitk Yann Dirson
2007-01-09 10:02 ` Catalin Marinas
2007-01-09 22:03 ` Yann Dirson
2007-01-10 10:34 ` Baz
2007-01-10 19:52 ` suggestions about stgit commands renaming Yann Dirson
2007-01-10 23:35 ` Catalin Marinas
2007-01-10 23:47 ` [PATCH] Add contrib/stg-gitk: helper script to run gitk Catalin Marinas
2007-01-12 22:47 ` Yann Dirson
2007-01-12 23:09 ` Catalin Marinas [this message]
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=b0943d9e0701121509t6d3ca059v9b7389ff3242c06b@mail.gmail.com \
--to=catalin.marinas@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 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).