From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git-log to go forward instead of reverse?
Date: 10 Jul 2006 12:25:33 -0700 [thread overview]
Message-ID: <86mzbhntxu.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607101212410.5623@g5.osdl.org>
>>>>> "Linus" == Linus Torvalds <torvalds@osdl.org> writes:
>> Wow. Yes, I think I can live with that for the application.
Linus> It's a big deal for me, I often end up doing things like
Linus> git log -p some-random-file
Linus> to see what has happened, and getting the most recent changes basically
Linus> instantaneously (rather than waiting for the thing to traverse all of the
Linus> history) is a big deal.
Well, this is for a "I'm connected to the net right now: please
refresh all of my git mirrors" script:
## (code here to cd to the right dir omitted)
git-fetch
if git-status | grep -v 'nothing to commit'
then echo UPDATE SKIPPED
else
if git-pull . origin | egrep -v 'up-to-date'
then git-log --pretty=short ORIG_HEAD..HEAD | cat
fi
fi
The log is just so I can quickly eyeball the interesting changes. The "cat"
is to keep git-log from starting a pager. (If there's a switch that does
*that* that I've overlooked, that'd be good too.)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2006-07-10 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 18:42 git-log to go forward instead of reverse? Randal L. Schwartz
2006-07-10 19:01 ` Linus Torvalds
2006-07-10 19:06 ` Randal L. Schwartz
2006-07-10 19:20 ` Linus Torvalds
2006-07-10 19:25 ` Randal L. Schwartz [this message]
2006-07-10 20:09 ` Linus Torvalds
2006-07-10 20:16 ` Randal L. Schwartz
2006-07-10 21:45 ` Junio C Hamano
2006-07-10 20:26 ` Junio C Hamano
2006-07-10 20:31 ` Randal L. Schwartz
2006-07-10 19:26 ` Linus Torvalds
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=86mzbhntxu.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).