From: <Peter.Dolland@mt.com>
To: <git@vger.kernel.org>
Cc: <notifications@github.com>
Subject: WG: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856)
Date: Tue, 2 Oct 2018 06:56:29 +0000 [thread overview]
Message-ID: <C19A54411B361046A786B5FA02D5689FE3B01FF9@ch00sem22.mt.mtnet> (raw)
In-Reply-To: <git-for-windows/git/issues/1856/426092877@github.com>
Please see my original observation below.
Is it possible, to extend the git-log syntax in the way, that it accepts the short -L option (without :file) of blame in unique cases (only one file is logged or respectively the -L expression may be valid for all logged files)? It would be nice for command line users!
Alternatively I could also imagine the extension of the blame functionality in the direction to see a whole history instead of only the last modification.
Best regards,
Peter Dolland
-----------------------
Von: Johannes Schindelin [mailto:notifications@github.com]
Gesendet: Dienstag, 2. Oktober 2018 01:06
An: git-for-windows/git
Cc: Dolland Peter MTPCE; Mention
Betreff: Re: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856)
It would be appropriate, but what @PhilipOakley asked you, @pdolland, was whether this is Windows-specific behavior. Because if it is not, then the feature request would be better sent to git@vger.kernel.org (the real Git mailing list; please make sure to send plain-text-only mails).
You saw fit to simply delete the issue reporting template instead of filling it out, so I have no way to assess whether WSL would be an option for you.
-----------
Von: Peter Dolland [mailto:notifications@github.com]
Gesendet: Montag, 1. Oktober 2018 13:26
An: git-for-windows/git
Cc: Dolland Peter MTPCE; Your activity
Betreff: Re: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856)
I have no possibility to check this on Linux.
However, I found out, that the documentation of the –L option is different for blame and log. The documented log –L is working, even if the output is not exactly, what I wanted. Nevertheless, I think it would be appropriate, to admit the syntax of blame for log too.
Best regards,
Peter Dolland
Von: Philip Oakley [mailto:notifications@github.com]
Gesendet: Montag, 1. Oktober 2018 13:04
An: git-for-windows/git
Cc: Dolland Peter MTPCE; Author
Betreff: Re: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856)
Have you been able to check if this issue is also present on Linux? It may be a a global Git problem rather than just a G-f-W issue.
I know there were some fairly recent upstream patches regarding the start,end aspects of the the '-L' option (IIRC mainly about the values spanning the end of the file).
There are a number of these options that do not carry fully between commands.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/git-for-windows/git/issues/1856#issuecomment-425868832>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADShEBzWN4hO6uC4frkbHUWfjC0iOccyks5ugfa0gaJpZM4XBvep>.
--------- <the original> ------------
Von: Peter Dolland [mailto:notifications@github.com]
Gesendet: Montag, 1. Oktober 2018 12:01
An: git-for-windows/git
Cc: Dolland Peter MTPCE; Your activity
Betreff: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856)
$ git log -L'/DRIVER_STATE = "/',+1 -- plm-dev/Wolke_M600_UTF8.java
fatal: -L argument not 'start,end:file' or ':funcname:file': /DRIVER_STATE = "/,+1
whereas blame with the same arguments does it:
$ git blame -L'/DRIVER_STATE = "/',+1 -- plm-dev/Wolke_M600_UTF8.java
51afb3c491 (Peter 2018-04-19 10:23:41 +0200 51) protected static final String DRIVER_STATE = "180419";
The same behavior with git versions 2.5.1 and 2.19.0.windows.1.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
next parent reply other threads:[~2018-10-02 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <git-for-windows/git/issues/1856@github.com>
[not found] ` <git-for-windows/git/issues/1856/426092877@github.com>
2018-10-02 6:56 ` Peter.Dolland [this message]
2018-10-02 14:43 ` WG: [git-for-windows/git] log -L/<regex>/,+1 not accepted (#1856) Jeff King
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C19A54411B361046A786B5FA02D5689FE3B01FF9@ch00sem22.mt.mtnet \
--to=peter.dolland@mt.com \
--cc=git@vger.kernel.org \
--cc=notifications@github.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://80x24.org/mirrors/git.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).