Re: Decreasing gains from git lost-found

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nicolas Pitre wrote:
On Tue, 11 Sep 2007, Andreas Ericsson wrote:

Nicolas Pitre wrote:

To me, the ability to say "HEAD@{35}" (or "HEAD@{650}"...) is not
fundamental,
Maybe it should?

Why? I'd have no idea where I'd end up. I can't remember exactly what I
did to my branch head more than 5 revs (or 15 minutes) ago, and since
the reflog provides "subject-by-action" instead of "subject-by-commit"
it's, imo, much less usable for recovering lost branch-heads.

Then, maybe you would be interested by 'git log -g' if 'git reflog' isn't verbose enough for you.


Ah, now this is more like it. I should have known someone would have
come up with something clever like that :)


Had I only remembered the exact wording in the commit-subject I'd
have found it a lot faster with "git-lost-found | grep wording" than
I would have if I'd used the reflog from the start.

Maybe 'git log -g -Swording' then?  Or any other log options you like.


*giggles* It works nicely with git-shortlog too.

--
Andreas Ericsson                   andreas.ericsson@xxxxxx
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux