From: Loic Fouray <loic@yeplaa.net>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org
Subject: Re: Merge conflict when lines next to each other are changed
Date: Wed, 1 Dec 2021 14:33:59 +0100 [thread overview]
Message-ID: <8E09F910-1D70-4848-A9E3-FA94B60335D3@yeplaa.net> (raw)
In-Reply-To: <008001d7e6ad$a155e290$e401a7b0$@nexbridge.com>
Thanks for your reply Randall.
If i understand correctly, you use externals tools (sed ..) but there is no possibility to manage It directly by git (spécific options,merge strategy..) , that’s right?
Regards
Loïc
> Le 1 déc. 2021 à 13:19, rsbecker@nexbridge.com a écrit :
>
> On December 1, 2021 4:30 AM, Loic Fouray wrote:
>> In a file, I have this 2 lines one below the other:
>>
>> Repository: myvalue
>> Tag: 8.2.10
>>
>> On my local branch i have updated repository myvalue.
>> On the upstream repo, they updated often the tag value (not updated of my
>> side).
>>
>> When i perform a merge from upstream to local branch, i have a conflit.
>> It seems that it’s related to neighboring lines.
>> Could you confirm that it ‘s a normal git operation?
>>
>> Also, i need to automate this merge. Is It possible with git tools to avoid this
>> conflict or to resolve this conflict automatically?
>
> I try to keep version-specific identifying information, which is already contained in git, out of my code. This includes change logs/history in each source file because git is good at keeping that information - it is redundant in the code. However, for organizations that need to do that, I suggest using clean/smudge filters so that the code inside the repository is clean, while things like the repo name and tag get injected into the code as git puts it into the working directory. The code is then cleaned up while being staged. This removes the possibility of the conflict on these lines by removing the differing lines. You can script this using a combination of sed and git commands. My own git front end does this all the time but it is not generally applicable to all platforms (only NonStop and MVS) so I have not contributed it.
>
> Regards,
> Randall
>
next prev parent reply other threads:[~2021-12-01 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:30 Merge conflict when lines next to each other are changed Loic Fouray
2021-12-01 12:18 ` rsbecker
2021-12-01 13:33 ` Loic Fouray [this message]
2021-12-01 14:09 ` rsbecker
2021-12-03 16:30 ` Loic Fouray
2021-12-03 16:52 ` rsbecker
2021-12-03 7:13 ` Jean-Noël Avila
2021-12-03 13:31 ` Loic Fouray
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=8E09F910-1D70-4848-A9E3-FA94B60335D3@yeplaa.net \
--to=loic@yeplaa.net \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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.
Code repositories for project(s) associated with this public 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).