From: Sergey Organov <sorganov@gmail.com>
To: Michael Salman <mjsalman@pathcom.com>
Cc: git@vger.kernel.org
Subject: Re: Merging problem
Date: Fri, 02 Aug 2024 23:53:56 +0300 [thread overview]
Message-ID: <87o76alk7v.fsf@osv.gnss.ru> (raw)
In-Reply-To: <3db395fe-8d32-4a33-8f16-7df95f3ff194@pathcom.com> (Michael Salman's message of "Fri, 2 Aug 2024 14:41:48 -0400")
Michael Salman <mjsalman@pathcom.com> writes:
> I am new to using git and I encountered the following problem
>
> 1) Created a repository using Notepad added a file (FileA.txt). Put one line of text in the file. Did a git commit -a. so far so good.
>
> 2) I created a branch (my-branch), did a git checkout my-branch
>
> 3) Using notepad loaded FileA and changed the first line of text to something else. Gave command git commit -a no problems
>
> 4) Git checkout master looked at FileA nothing changed
>
> 5) Did a git merge my-branch. No conflict reported
>
> 6) Loaded FileA in master the text of the first line had changed to what is in FileA from the branch
>
> Your help with this problem would be appreciated. I hope this is not
> due to my lack of understanding
You didn't tell us what outcome you expected, but to me all looks fine:
you've merged your changes (made at step 3) from side branch to the
master branch, and now your changes (made at step 3) are there on the
master branch as well: that's the whole purpose of merges.
As there were no any changes on master, there is nothing there for a
potential conflict, so all went pretty smooth, as expected. If you
change first line of the file in notepad (differently from step 3)
between steps 4 and 5 as well, and commit your changes, you will then
get conflict during merge.
-- Sergey Organov
prev parent reply other threads:[~2024-08-02 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 18:41 Merging problem Michael Salman
2024-08-02 20:00 ` brian m. carlson
2024-08-02 20:04 ` rsbecker
2024-08-02 20:53 ` Sergey Organov [this message]
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=87o76alk7v.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
--cc=mjsalman@pathcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.