From: Junio C Hamano <gitster@pobox.com>
To: Prasad Pandit <pjp@fedoraproject.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: File missing from git branch
Date: Wed, 01 Jan 2025 08:53:59 -0800 [thread overview]
Message-ID: <xmqq1pxmxyoo.fsf@gitster.g> (raw)
In-Reply-To: <1964163554.5326830.1735643984559@mail.yahoo.com> (Prasad Pandit's message of "Tue, 31 Dec 2024 11:19:44 +0000 (UTC)")
Prasad Pandit <pjp@fedoraproject.org> writes:
> * Generally committed local changes are visible across local
> branches, right? Is there a way to see/access those locally added
> files across local branches?
Not at all.
In fact, the contents on branch A is unmolested by the act of
committing changes on branch B. They are independent lines of
development. Otherwise your version control system is broken.
Until you decide to consolidate the change you made on branch A
into branch B, that is. People call that operation "merging branch
A to branch B".
next prev parent reply other threads:[~2025-01-01 16:54 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 ` File missing from git branch Prasad Pandit
2025-01-01 16:53 ` Junio C Hamano [this message]
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=xmqq1pxmxyoo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pjp@fedoraproject.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).