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
On Monday 2012-07-30 14:11, Thomas Badie wrote:
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
Jan Engelhardt jeng...@inai.de writes:
On Monday 2012-07-30 14:11, Thomas Badie wrote:
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
Thomas Badie thomas.ba...@gmail.com writes:
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
2012/7/30 Jan Engelhardt jeng...@inai.de:
On Monday 2012-07-30 14:11, Thomas Badie wrote:
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
2012/7/30 Sitaram Chamarty sitar...@gmail.com:
On Mon, Jul 30, 2012 at 5:41 PM, Thomas Badie thomas.ba...@gmail.com wrote:
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
On Mon, Jul 30, 2012 at 06:40:12PM +0200, Thomas Badie wrote:
I understand your opinion. My solution was a easier way to make your
proposition about `git log --oneline`, because I don't want to copy these
6 numbers by hand. I'd prefer select the right line simply.
My solution is intended
2012/7/30 Junio C Hamano gits...@pobox.com:
Jan Engelhardt jeng...@inai.de writes:
On Monday 2012-07-30 14:11, Thomas Badie wrote:
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,
2012/7/30 Thomas Rast tr...@student.ethz.ch:
Thomas Badie thomas.ba...@gmail.com writes:
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
2012/7/30 Jeff King p...@peff.net:
On Mon, Jul 30, 2012 at 06:40:12PM +0200, Thomas Badie wrote:
I understand your opinion. My solution was a easier way to make your
proposition about `git log --oneline`, because I don't want to copy these
6 numbers by hand. I'd prefer select the right line
Thomas Badie thomas.ba...@gmail.com writes:
For this case, I don't think I'll use it, but it shows how to use the editor
in a replacement of an interactive tool, and it is interesting. I'd change
vi for emacs but this is religious.
If you use emacs anyway you could run the shell inside it,
On Mon, Jul 30, 2012 at 11:45 AM, Junio C Hamano gits...@pobox.com wrote:
git show -s ':/^t1100-.*: Fix an interm'
That doesn't work for me (git 1.7.10.4 as per Fedora 18 rpms) in
git.git. But the idea is sound -- git can give you the sha1 trivially.
You don't need additional glue.
But
Martin Langhoff martin.langh...@gmail.com writes:
On Mon, Jul 30, 2012 at 11:45 AM, Junio C Hamano gits...@pobox.com wrote:
git show -s ':/^t1100-.*: Fix an interm'
That doesn't work for me (git 1.7.10.4 as per Fedora 18 rpms) in
git.git. But the idea is sound -- git can give you the
Martin Langhoff martin.langh...@gmail.com writes:
But any ref definition can be turned into a sha1 with this snippet:
git show --pretty=format:%H HEAD
git rev-parse HEAD
If you want to get the last 10 sha1s, use the same pretty with git log
git log --pretty=format:%H HEAD |
On Mon, Jul 30, 2012 at 2:29 PM, Junio C Hamano gits...@pobox.com wrote:
The idea was that you do not have to give abbreviated SHA-1 to Git
in the first place.
Ah, sorry, I didn't get _that_ point. I thought you were trying to
demo a way to get a sha1.
What doesn't work? My copy of v1.7.10.1
15 matches
Mail list logo
