From: Thomas Badie <thomas.badie@gmail.com>
To: git@vger.kernel.org
Subject: A new way to get a sha1?
Date: Mon, 30 Jul 2012 14:11:30 +0200 [thread overview]
Message-ID: <jv5tln$96e$1@dough.gmane.org> (raw)
Hi all,
When I should fixup or squash a commit, I nearly never
remember how to get the sha1 of the commit I want to fixup.
Because sometimes HEAD~n is not enough, I make `git log`,
copy the sha1 of the right commit and paste it in my git
fixup command. So I wrote a perl script to avoid the usage
of the mouse. And after discussion with some of my friends,
this can be generalized as a generic command line interface
tool to get a sha1.
The idea is to have a perl module which run through
the log history and print 10 shortlog associated with a number
from 0 to 9, and a message below "Select commit [| 0, 9 |] or
next row ?" or this kind of message with several options.
So I ask to the community if this module is interesting for git.
It can be integrated everywhere a sha1 is requested (git rebase,
git reset, ...). IMHO, it can be an enhancement.
So, what is your opinion? Should I make this script a perl module
and integrate it in git, or should I just keep it in my own script
toolbox?
Thanks for reading and answering,
--
Thomas "Enki" Badie
next reply other threads:[~2012-07-30 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 12:11 Thomas Badie [this message]
2012-07-30 12:28 ` A new way to get a sha1? Jan Engelhardt
2012-07-30 15:45 ` Junio C Hamano
2012-07-30 16:57 ` Thomas Badie
2012-07-30 18:16 ` Martin Langhoff
2012-07-30 18:29 ` Junio C Hamano
2012-07-30 18:42 ` Martin Langhoff
2012-07-30 18:40 ` Andreas Schwab
2012-07-30 16:40 ` Thomas Badie
2012-07-30 16:51 ` Jeff King
2012-07-30 17:33 ` Thomas Badie
2012-07-30 17:55 ` Andreas Schwab
2012-07-30 12:41 ` Sitaram Chamarty
2012-07-30 16:49 ` Thomas Badie
2012-07-30 15:57 ` Thomas Rast
2012-07-30 17:17 ` Thomas Badie
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='jv5tln$96e$1@dough.gmane.org' \
--to=thomas.badie@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 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).