[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git apologia
From: |
Andreas Schwab |
Subject: |
Re: git apologia |
Date: |
Mon, 17 Nov 2014 17:50:55 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
> When I pull from upstream, I almost always look at the log summary
> lines of the last dozen commits, and then frequently examine one or
> more of those in detail. So I need a quick and convenient method of
> doing "git show" or its equivalent without the need to type the 7 hex
> characters of the SHA1 checksum. What's more natural than asking for
> the Nth previous commit?
Copy and paste from the output of git pull, which tells you exactly what
has changed. Pass that to git log.
Andreas.
--
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
- Re: git apologia, (continued)
- Re: git apologia, Eli Zaretskii, 2014/11/16
- Re: git apologia, Andreas Schwab, 2014/11/16
- Re: git apologia, Eli Zaretskii, 2014/11/16
- Re: git apologia, Andreas Schwab, 2014/11/16
- Re: git apologia, Eli Zaretskii, 2014/11/16
- Re: git apologia, Andreas Schwab, 2014/11/16
- Re: git apologia, Eli Zaretskii, 2014/11/16
- Re: git apologia, Teemu Likonen, 2014/11/16
- Re: git apologia, Stephen J. Turnbull, 2014/11/16
- Re: git apologia, Eli Zaretskii, 2014/11/17
- Re: git apologia,
Andreas Schwab <=
- Re: git apologia, Eli Zaretskii, 2014/11/17
- Re: git apologia, David Kastrup, 2014/11/17
- Re: git apologia, Achim Gratz, 2014/11/17
- Re: git apologia, Yuri Khan, 2014/11/17
- Re: git apologia, Thien-Thi Nguyen, 2014/11/18
- Re: git apologia, John Yates, 2014/11/18
- Re: git apologia, Thien-Thi Nguyen, 2014/11/18
- Re: git apologia, Andreas Schwab, 2014/11/18
- Re: git apologia, Barry Warsaw, 2014/11/18
- Re: git pull fails with merge conflicts. How can this possibly happen?, Sergey Organov, 2014/11/17