git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Levedahl <mlevedahl@gmail.com>
To: Allan Ford <Allan.Ford@hambs.com.au>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GitGui tool - new local clone is missing commit(s) and missing a tag on master branch
Date: Sat, 10 Feb 2024 14:10:59 -0500	[thread overview]
Message-ID: <b5c93203-633f-405b-9bb3-1f8be87c16d6@gmail.com> (raw)
In-Reply-To: <MEYPR01MB6534B74E07CB2231EAE8D5C7A5452@MEYPR01MB6534.ausprd01.prod.outlook.com>

On 2/7/24 01:00, Allan Ford wrote:
> Dear Git devs,
> 
> GitGui tool local clone is missing commit(s) and missing a tag on master branch
>   
> As compared to using Visual Studio 2022 or Visual Studio Code ..
> Wondering if a bug somehow / somewhere ?
> Other colleague devs observe the same ..
> 
> If I switch to the remote master branch then I get right content ..   but I should be able to do a new clone of master and hold locally.

This is reminiscent of cloning issues some folks on my team raised 
nearly a decade ago. git-gui uses a custom/unique do_clone function 
written in tcl, rather than native git-clone, so problem diagnosis is 
difficult and updates infrequent. My "cure" was to make git-gui use 
git-clone. I still have that patch, have rebased it (some conflicts) 
onto current git-gui master, and it still works in my very limited testing.

But, git-gui currently has no active maintainer, and Junio is now in a 
release cycle, so the list's concern is not on new topics like this. For 
both reasons, I'll hold onto the patch until the release cycle completes.

Mark

      reply	other threads:[~2024-02-10 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  6:00 GitGui tool - new local clone is missing commit(s) and missing a tag on master branch Allan Ford
2024-02-10 19:10 ` Mark Levedahl [this message]

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=b5c93203-633f-405b-9bb3-1f8be87c16d6@gmail.com \
    --to=mlevedahl@gmail.com \
    --cc=Allan.Ford@hambs.com.au \
    --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).