git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Pharaoh <apollosoftware64@gmail.com>
To: git@vger.kernel.org
Subject: Git Subtree Bug Report
Date: Sat, 10 Sep 2022 05:46:50 -0400	[thread overview]
Message-ID: <EC3D3822-0CA7-405A-9F88-22312414C856@gmail.com> (raw)

[-- Attachment #1: git-bugreport-2022-09-10-0538.txt --]
[-- Type: text/plain, Size: 1485 bytes --]

hank 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? (Steps to reproduce your issue)
Used git subtree command normally, re-add subtree into parent repository.
Then I tried to push changes I commited inside subtree directory and it keeps saying git push using:  velocity dev/3.0.0
cache for 74edac9642c1318ff038da0ae5dc1d543d42624e already exists!

Issue can be found and report here as well: https://stackoverflow.com/questions/68761778/git-subtree-cache-exists
What did you expect to happen? (Expected behavior)
For subtree to push changes to remote
What happened instead? (Actual behavior)
Cache exist!
What's different between what you expected and what actually happened?
It used to work on older version and now it currently does not on this one.
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.37.3
cpu: arm64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64
compiler info: clang: 13.1.6 (clang-1316.0.21.2.5)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh


[Enabled Hooks]

                 reply	other threads:[~2022-09-10  9:47 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

  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=EC3D3822-0CA7-405A-9F88-22312414C856@gmail.com \
    --to=apollosoftware64@gmail.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.
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).