From: Abhijeet Sonar <abhijeet.nkt@gmail.com>
To: git@vger.kernel.org
Cc: Paul Millar <paul.millar@desy.de>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] describe: refresh the index when 'broken' flag is used
Date: Mon, 24 Jun 2024 03:26:32 +0530 [thread overview]
Message-ID: <7e3ba9fc-1ff4-49aa-8e73-c50202477719@gmail.com> (raw)
In-Reply-To: <20240623214301.143796-1-abhijeet.nkt@gmail.com>
This is my first ever patch submission and I am excited to contribute
even if it is such a little thing! Please let me know of any etiquette
or convention violations, I will do my best to uphold them moving forward.
Thanks
On 24/06/24 03:12, Abhijeet Sonar wrote:
> When describe is run with 'dirty' flag, we refresh the index
> to make sure it is in sync with the filesystem before
> determining if the working tree is dirty. However, this is
> not done for the codepath where the 'broken' flag is used.
>
> This causes `git describe --broken --dirty` to false
> positively report the worktree being dirty. Refreshing the
> index before running diff-index fixes the problem.
>
> Signed-off-by: Abhijeet Sonar <abhijeet.nkt@gmail.com>
> Reported-by: Paul Millar <paul.millar@desy.de>
> Suggested-by: Junio C Hamano <gitster@pobox.com>
> ---
> builtin/describe.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/builtin/describe.c b/builtin/describe.c
> index e5287eddf2..2b443c155e 100644
> --- a/builtin/describe.c
> +++ b/builtin/describe.c
> @@ -645,6 +645,20 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
> if (argc == 0) {
> if (broken) {
> struct child_process cp = CHILD_PROCESS_INIT;
> + struct lock_file index_lock = LOCK_INIT;
> + int fd;
> +
> + setup_work_tree();
> + prepare_repo_settings(the_repository);
> + repo_read_index(the_repository);
> + refresh_index(the_repository->index, REFRESH_QUIET|REFRESH_UNMERGED,
> + NULL, NULL, NULL);
> + fd = repo_hold_locked_index(the_repository,
> + &index_lock, 0);
> + if (0 <= fd)
> + repo_update_index_if_able(the_repository, &index_lock);
> +
> +
> strvec_pushv(&cp.args, diff_index_args);
> cp.git_cmd = 1;
> cp.no_stdin = 1;
next prev parent reply other threads:[~2024-06-23 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 21:42 [PATCH] describe: refresh the index when 'broken' flag is used Abhijeet Sonar
2024-06-23 21:56 ` Abhijeet Sonar [this message]
2024-06-24 10:56 ` Karthik Nayak
2024-06-24 11:20 ` Phillip Wood
2024-06-24 12:20 ` Abhijeet Sonar
2024-06-24 13:48 ` Abhijeet Sonar
2024-06-24 16:34 ` Junio C Hamano
2024-06-24 17:37 ` Abhijeet Sonar
2024-06-24 17:58 ` Junio C Hamano
2024-06-25 6:40 ` Abhijeet Sonar
2024-06-25 6:44 ` [PATCH v2] " Abhijeet Sonar
2024-06-25 12:27 ` Karthik Nayak
2024-06-25 13:22 ` Abhijeet Sonar
2024-06-25 12:28 ` [PATCH] " Karthik Nayak
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=7e3ba9fc-1ff4-49aa-8e73-c50202477719@gmail.com \
--to=abhijeet.nkt@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paul.millar@desy.de \
--cc=peff@peff.net \
/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).