2012/7/30 Jeff King :
> 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 p
2012/7/30 Thomas Rast :
> Thomas Badie 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 t
2012/7/30 Junio C Hamano :
> Jan Engelhardt 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 fi
2012/7/30 Sitaram Chamarty :
> On Mon, Jul 30, 2012 at 5:41 PM, 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
2012/7/30 Jan Engelhardt :
> 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 ma
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
o
6 matches
Mail list logo
