From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Mathias Megyei <mathias@mnet-mail.de>,
Emacs developers <emacs-devel@gnu.org>,
Stephen Berman <stephen.berman@gmx.net>,
Andreas Schwab <schwab@linux-m68k.org>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: git log question
Date: Thu, 30 Nov 2017 17:59:48 +0000 [thread overview]
Message-ID: <CAFyQvY2q9rp8mYpJL7i_Zo736e+2Jdi7H5RTis12XgPK=peeVA@mail.gmail.com> (raw)
In-Reply-To: <8a1b2194-4bc1-ebae-ec18-9d5566388991@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Thu, Nov 30, 2017 at 12:46 PM Clément Pit-Claudel <cpitclaudel@gmail.com>
wrote:
> On 2017-11-30 10:21, Kaushal Modi wrote:
> > 3. C-s b407c521f2 (the commit you are interested in).
>
> That usually doesn't work in my experience (Magit doesn't show all commits
> in the log, only the last ~250).
>
That of course was a "quick and dirty way". I mentioned this approach
because it was about sleuthing a recent commit.
'lb' has now become a goto to do all sorts of things: branching, merging,
cherry picking, interactive rebase, quickly doing n/p in the log to see
commit details in the other window.. and this particular use case fit in
too..
YMMW, but the first thing I do almost always after M-x magit-status is lb
followed by fa.
Also, the method Noam mentioned is spot on: M-x magit-show-commi.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1315 bytes --]
next prev parent reply other threads:[~2017-11-30 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 10:00 git log question Stephen Berman
2017-11-30 11:30 ` Mathias Megyei
2017-11-30 12:02 ` Stephen Berman
2017-11-30 13:15 ` Yuri Khan
2017-11-30 14:19 ` Stephen Berman
2017-11-30 14:59 ` Noam Postavsky
2017-11-30 15:05 ` Yuri Khan
2017-11-30 15:05 ` Andreas Schwab
2017-11-30 15:21 ` Kaushal Modi
2017-11-30 15:25 ` Andreas Schwab
2017-11-30 15:35 ` Noam Postavsky
2017-11-30 17:46 ` Clément Pit-Claudel
2017-11-30 17:59 ` Kaushal Modi [this message]
2017-11-30 17:06 ` Davis Herring
2017-11-30 19:11 ` Stephen Berman
2017-11-30 14:28 ` Herring, Davis
2017-11-30 14:37 ` Stephen Berman
2017-11-30 15:57 ` Eli Zaretskii
2017-11-30 19:10 ` Stephen Berman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY2q9rp8mYpJL7i_Zo736e+2Jdi7H5RTis12XgPK=peeVA@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mathias@mnet-mail.de \
--cc=schwab@linux-m68k.org \
--cc=stephen.berman@gmx.net \
--cc=yuri.v.khan@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).