From: Junio C Hamano <gitster@pobox.com>
To: amishera <amishera2007@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How are the same file modified on different brances stored physically?
Date: Mon, 03 Mar 2008 01:06:05 -0800 [thread overview]
Message-ID: <7vskz8i3cy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <15799383.post@talk.nabble.com> (amishera2007@gmail.com's message of "Mon, 3 Mar 2008 00:16:49 -0800 (PST)")
amishera <amishera2007@gmail.com> writes:
> I am trying to figure out how stuffs work behind the scene. We know that we
> can switch branches freely and then work on the switched branch. If the same
> file is modified on two branches then how are the two copies of the two
> branches saved?
They are saved separately, and depending on which branch you check out, the
appropriate one for that branch is given to you.
next prev parent reply other threads:[~2008-03-03 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 8:16 How are the same file modified on different brances stored physically? amishera
2008-03-03 9:06 ` Junio C Hamano [this message]
2008-03-03 9:36 ` Mike Ralphson
2008-03-03 12:10 ` Jakub Narebski
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=7vskz8i3cy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=amishera2007@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.
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).