git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prasad Pandit <pjp@fedoraproject.org>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: File missing from git branch
Date: Tue, 31 Dec 2024 11:19:44 +0000 (UTC)	[thread overview]
Message-ID: <1964163554.5326830.1735643984559@mail.yahoo.com> (raw)
In-Reply-To: 1964163554.5326830.1735643984559.ref@mail.yahoo.com

Hi,

Kernel-ark -> https://gitlab.com/cki-project/kernel-ark/

* I have forked the kernel-ark git repository. The forked tree is regularly updated by pulling commits from its upstream repository above. I have added/committed couple of config files under '../arch/x86/configs/' directory in the forked tree, not in the above upstream repository. Let's say

   Fork was created on - day-0
   Files were added on - day-1
   Updates are pulled  - day-2, day-3, day-4 ... day-n

* The issue is: the config files I added are visible only in the main (os-build) branch. If I create a new branch with

   $ git branch new-branch <commit-hash/merge-hash/commit-tag/>

Those config files are not visible/accessible under '../arch/x86/configs' directory.

   Note => Files are added and branches are created on the same forked tree.

* Generally committed local changes are visible across local branches, right? Is there a way to see/access those locally added files across local branches?

* Is there a different way to do this?

Thank you.
---
  -Prasad

       reply	other threads:[~2024-12-31 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1964163554.5326830.1735643984559.ref@mail.yahoo.com>
2024-12-31 11:19 ` Prasad Pandit [this message]
2025-01-01 16:53   ` File missing from git branch Junio C Hamano
2025-01-02 10:11     ` Prasad Pandit
2025-01-02 11:40       ` Chris Torek
2025-01-03 10:26         ` Prasad Pandit

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=1964163554.5326830.1735643984559@mail.yahoo.com \
    --to=pjp@fedoraproject.org \
    --cc=git@vger.kernel.org \
    --cc=pj.pandit@yahoo.in \
    /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).