From: Michael Garza <michael.garza.embv@statefarm.com>
To: "'git@vger.kernel.org'" <git@vger.kernel.org>
Cc: Michael Garza <michael.garza.embv@statefarm.com>
Subject: RE: Submit Git Bug
Date: Tue, 21 Jul 2020 19:53:02 +0000 [thread overview]
Message-ID: <bae4a7fd47f948e1856aec69a51b2ff0@statefarm.com> (raw)
In-Reply-To: <65b88444bf544024a434dbc25bd6a487@statefarm.com>
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? Initiated the cp.exe command to copy file(s) from one location to another.
What did you expect to happen? I expected to see in the Windows Sysmon Event 1 the entire command string.
What happened instead? The log captured is only that cp.exe was used.
What's different between what you expected and what actually happened? The difference is that the entire command string is not being captured.
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.27.0.windows.1
cpu: x86_64
built from commit: 907ab1011dce9112700498e034b974ba60f8b407
sizeof-long: 4
sizeof-size_t: 8
uname: Windows 10.0 18363
compiler info: gnuc: 10.1
libc info: no libc information available
[Enabled Hooks]
not run from a git repository - no hooks to show
Thanks,
Michael Garza,
next parent reply other threads:[~2020-07-21 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65b88444bf544024a434dbc25bd6a487@statefarm.com>
2020-07-21 19:53 ` Michael Garza [this message]
2021-01-07 13:00 ` Submit Git Bug Johannes Schindelin
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=bae4a7fd47f948e1856aec69a51b2ff0@statefarm.com \
--to=michael.garza.embv@statefarm.com \
--cc=git@vger.kernel.org \
/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).