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@xxxxxxxxxx] 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@xxxxxxxxxxxxxxx (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@xxxxxxxxxx] 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@xxxxxxxxxx] 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@xxxxxxxxxx] 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.
