public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: check_reparse_point_target: fix comment format Date: Tue, 20 Dec 2022 21:54:31 +0000 (GMT) [thread overview] Message-ID: <20221220215431.DC1363858421@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=fd3ce87f734526e1fd389c027f189a21e6e01322 commit fd3ce87f734526e1fd389c027f189a21e6e01322 Author: Corinna Vinschen <corinna@vinschen.de> AuthorDate: Mon Dec 19 12:47:42 2022 +0100 Commit: Corinna Vinschen <corinna@vinschen.de> CommitDate: Tue Dec 20 10:13:59 2022 +0100 Cygwin: check_reparse_point_target: fix comment format Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/cygwin/path.cc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/winsup/cygwin/path.cc b/winsup/cygwin/path.cc index c044d5295ed5..4df389bba257 100644 --- a/winsup/cygwin/path.cc +++ b/winsup/cygwin/path.cc @@ -2565,10 +2565,10 @@ check_reparse_point_target (HANDLE h, bool remote, PREPARSE_DATA_BUFFER rp, } if (rp->ReparseTag == IO_REPARSE_TAG_SYMLINK) { - /* Windows evaluates native symlink literally. If a remote symlink points - to, say, C:\foo, it will be handled as if the target is the local file - C:\foo. That comes in handy since that's how symlinks are treated under - POSIX as well. */ + /* Windows evaluates native symlink literally. If a remote symlink + points to, say, C:\foo, it will be handled as if the target is the + local file C:\foo. That comes in handy since that's how symlinks + are treated under POSIX as well. */ RtlInitCountedUnicodeString (psymbuf, (PWCHAR)((PBYTE) rp->SymbolicLinkReparseBuffer.PathBuffer + rp->SymbolicLinkReparseBuffer.SubstituteNameOffset),
reply other threads:[~2022-12-20 21:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221220215431.DC1363858421@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).