From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Victor Porton" <porton.victor@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log --patch for a particular file
Date: Mon, 16 Oct 2023 12:29:43 +0200 [thread overview]
Message-ID: <d34d9b64-4760-43e8-975c-a3ef53048530@app.fastmail.com> (raw)
In-Reply-To: <75545e1c-ce62-4b49-983e-1e7b1afb2fab@gmail.com>
Hi
On Mon, Oct 16, 2023, at 12:20, Victor Porton wrote:
> I want this:
>
> git log --patch -- server/src/api/docs.py
>
> to print changes only for the file server/src/api/docs.py.
That's how it works for me.
> Currently, it in some reasons outputs nothing (this seems not to be an
> intended behavior and could be counted as a bug).
Does it output nothing on *merge* commits? That's intended.
Try using `-m` as well.
https://stackoverflow.com/a/37801468/1725151
> It is questionable, whether to output commit information (commit hash,
> user email, etc.) for commits that don't change specified file(s). I
> would vote to indeed output this information, not to confuse the user
> about the order of commits.
You can customize the output with `--format=`.
> More generally,
> git log --patch -- A B C
> could log changes in files A, B, C (only).
If I name two files I only get commits that touch any of those files. And
diffs only for them.
--
Kristoffer Haugsbakk
prev parent reply other threads:[~2023-10-16 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 10:20 git log --patch for a particular file Victor Porton
2023-10-16 10:29 ` Kristoffer Haugsbakk [this message]
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=d34d9b64-4760-43e8-975c-a3ef53048530@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=porton.victor@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.
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).