git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Tiran Meltser <Tiran.Meltser@mavenir.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Cc: Amir Yosef <Amir.Yosef@mavenir.com>
Subject: Excluding files from Git merge
Date: Thu, 11 Jun 2020 14:31:52 +0000	[thread overview]
Message-ID: <DM6PR11MB27959B6BE6ABDB1F79238126E5800@DM6PR11MB2795.namprd11.prod.outlook.com> (raw)

Hi,
This topic is quite common in various use cases (e.g. production configuration vs. staging one) and there are quite a few talks about it in the web.
Nevertheless, there is no specific solution to this problem, only partial workarounds (including the famous merge driver “ours”).

I would like to suggest adding the git a simple and precise handling for the need to mark file(s)/folder(s) that are branch specific and should not be involved in merge operation at all.

2 suggestions I can think of are (but any good solution would suffice):
• Adding additional merge strategy indication the file/folder is excluded from merges (e.g. merge=disabled/none/skip/…)
• Adding a new configuration file (like .gitignore) for tracking these special files/folders, for example: .gitisolate/.gitquarantine/.gitbranchspecific/.gitsilo/…

Any comment would be appreciated.



Tiran Meltser
System Architect, Global Products & Operations





t   tel:+441189308826
m tel:+447894604040
e  mailto:maria.hudson@mavenir.com


________________________________
This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to security@mavenir.com. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects. Thank You

                 reply	other threads:[~2020-06-11 14:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DM6PR11MB27959B6BE6ABDB1F79238126E5800@DM6PR11MB2795.namprd11.prod.outlook.com \
    --to=tiran.meltser@mavenir.com \
    --cc=Amir.Yosef@mavenir.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.
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).