From: Jeff King <peff@peff.net>
To: Julien Richard <julien.richard@ubisoft.com>
Cc: Julien Richard via GitGitGadget <gitgitgadget@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Julien Richard <jairbubbles@hotmail.com>
Subject: Re: [PATCH] doc: 'T' status code for git status
Date: Wed, 9 Dec 2020 13:35:29 -0500 [thread overview]
Message-ID: <X9EY8fBoLHIa68WY@coredump.intra.peff.net> (raw)
In-Reply-To: <BYAPR17MB26461C4578004C8C223249DB9DCC0@BYAPR17MB2646.namprd17.prod.outlook.com>
On Wed, Dec 09, 2020 at 06:01:36PM +0000, Julien Richard wrote:
> > Perhaps "type changed (e.g., a symbolic link becoming a file)" would be more descriptive
>
> In fact I'm not sure how get the typechange, I always see the symbolic
> link example but in my case I have a 100% repro on a repository but
> ZI have no clue why its does so.
> The file is just modified but appears as a type change :-S
>
> Could it be a bug?
Possibly. If you have a reproduction recipe, share it and we can comment
further.
> About the changes you mentioned should I make the adjustements myself?
Yes, usually you'd squash in any changes you want to make using "commit
--amend" (or "rebase -i", but you only have one patch in the series),
and then you can resubmit via GitGitGadget.
-Peff
next prev parent reply other threads:[~2020-12-09 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 8:13 [PATCH] doc: 'T' status code for git status Julien Richard via GitGitGadget
2020-12-09 17:37 ` Jeff King
2020-12-09 18:01 ` Julien Richard
2020-12-09 18:35 ` Jeff King [this message]
2020-12-09 20:26 ` Junio C Hamano
2020-12-09 20:56 ` Julien Richard
2020-12-09 21:32 ` Jeff King
2020-12-10 0:47 ` Junio C Hamano
2020-12-09 19:12 ` [PATCH v2] " Julien Richard via GitGitGadget
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=X9EY8fBoLHIa68WY@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jairbubbles@hotmail.com \
--cc=julien.richard@ubisoft.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).