From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: qgit idea: interface for cherry-picking
Date: Tue, 04 Jul 2006 15:29:28 +0200 [thread overview]
Message-ID: <e8dqfo$3ff$1@sea.gmane.org> (raw)
In-Reply-To: e5bfff550607040458m1e6ea6bes44b3e3eba26856f0@mail.gmail.com
Marco Costalba wrote:
> In the past weeks I (with Pavel support) have implemented and pushed
> the concept of "custom actions".
>
> Is it possible to associate commands sequences, scripts and anything
> else executable to a custom action. Actions can be called and run from
> menu entry and corresponding output is grabbed by a terminal window.
>
> Instead of hard code each git-native command, this way you have a
> flexible framework to add shortcuts and menu entry for anything you
> would like to be a click away. BTW I use this for stuff like git pull,
> but also for 'make' and 'make install' because you have a window
> terminal for feedback.
>
> There is also the possibility to input command line parameters before
> to run, useful, as example for a git pull action that asks for source
> repository to pull from.
>
> Is this something that can fulfill you request? do you need something
> different? perhaps something as a "default to current selected SHA as
> input argument" flag.
It would be nice (I don't know if feasible) that either to provide some kind
of parameters substitution in the likes of "%head" in the invocation line
for a script to be expanded to the sha1 or name of head of currently
selected commit.
Other solution would be to provide GUI for input of command line parameters,
e.g. combo-box (i.e. editable text field, with provided list of default
values) for repository (populated from .git/branches and .git/remotes),
option to select commit or use selected commit for head ref or just commit
ref, etc...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-04 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 19:01 qgit idea: interface for cherry-picking Jakub Narebski
2006-07-02 21:33 ` Marco Costalba
2006-07-02 21:46 ` Jakub Narebski
2006-07-02 22:04 ` Marco Costalba
2006-07-02 22:54 ` Jakub Narebski
2006-07-03 5:45 ` Marco Costalba
2006-07-03 6:42 ` Junio C Hamano
2006-07-03 11:18 ` Marco Costalba
2006-07-03 20:03 ` Junio C Hamano
2006-07-04 6:22 ` Marco Costalba
2006-07-04 6:39 ` Jakub Narebski
2006-07-04 11:58 ` Marco Costalba
2006-07-04 13:29 ` Jakub Narebski [this message]
2006-07-04 18:38 ` Marco Costalba
2006-07-04 6:41 ` Junio C Hamano
2006-07-04 7:02 ` Jakub Narebski
2006-07-04 11:21 ` Marco Costalba
2006-07-04 18:23 ` Marco Costalba
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='e8dqfo$3ff$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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.