git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Wolfgang Graf <wg@wogra.net>
To: git@vger.kernel.org
Subject: Sequent  repos ,, pull without checkout
Date: Thu, 03 Sep 2020 08:38:59 +0200	[thread overview]
Message-ID: <20200903083859.Horde.d_JTRsvdjC38RffOwMv54lJ@webmail.your-server.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]


What did you do before the bug happened? (Steps to reproduce your issue)


We have three repos bt,bt2,bt3 where bt2 is a clone of bt and bt3 is a  
clone of bt2.
All remote destinations remain unchanged (pointing to the repo before).

Step 1: I'm creating a branch "b11" in bt, committing it.
Step 2: Going to bt2, doing git pull --all.
Step 3: Going to bt3, doing git pull --all.


What did you expect to happen? (Expected behavior)

The branch b11 is usable in bt3 also

What happened instead? (Actual behavior)

Either doing
Step 2a: If I'm doing a git checkout b11 in bt2 before Step 3
The branch b11 is also usable in bt3
This works

or doing
Step 2b: If I'm doing a fetch by name 'fetch origin master:master bt11:bt11"
This works

But if I'm only pushing through from bt to bt3 without doing checkout in bt2
the b11 is no more usable in bt3 when omitting step 2a or2b


What's different between what you expected and what actually happened?

The pull output did show me that there changes are tracked. But
only if a checkout in bt2 in the middle was made before the content
of the changes made within the origin change are really coming through to bt3



Anything else you want to add:

This might not be necessarily a bug. If this behavior is intended please
close it. It would be instead of that be nice if some guideline would exist
to deal with changes wired through a cascade of repositories in  
different branches.
As seen on the internet many people are asking for a solution for that.


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.28.0.windows.1
cpu: x86_64
built from commit: 77982caf269b7ee713a76da2bcf260c34d3bf7a7
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
uname: Windows 10.0 18362
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe


[Enabled Hooks]
-


Kind regards

Wolfgang

wg@wogra.net


-- 
**
I prefer signed and encrypted email messages.
If you are able to recieve encryted messages please let me know.
**

[-- Attachment #2: S/MIME-Signatur --]
[-- Type: application/pkcs7-signature, Size: 3185 bytes --]

             reply	other threads:[~2020-09-03  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  6:38 Wolfgang Graf [this message]
2020-09-03 22:25 ` Raymond E. Pasco

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=20200903083859.Horde.d_JTRsvdjC38RffOwMv54lJ@webmail.your-server.de \
    --to=wg@wogra.net \
    --cc=git@vger.kernel.org \
    --subject='Re: Sequent  repos ,, pull without checkout' \
    /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

Code repositories for project(s) associated with this 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).