head	1.2;
access;
symbols
	pkgsrc-2026Q1:1.2.0.16
	pkgsrc-2026Q1-base:1.2
	pkgsrc-2025Q4:1.2.0.14
	pkgsrc-2025Q4-base:1.2
	pkgsrc-2025Q3:1.2.0.12
	pkgsrc-2025Q3-base:1.2
	pkgsrc-2025Q2:1.2.0.10
	pkgsrc-2025Q2-base:1.2
	pkgsrc-2025Q1:1.2.0.8
	pkgsrc-2025Q1-base:1.2
	pkgsrc-2024Q4:1.2.0.6
	pkgsrc-2024Q4-base:1.2
	pkgsrc-2024Q3:1.2.0.4
	pkgsrc-2024Q3-base:1.2
	pkgsrc-2024Q2:1.2.0.2
	pkgsrc-2024Q2-base:1.2
	pkgsrc-2024Q1:1.1.0.12
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.10
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.8
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.6
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.4
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.2
	pkgsrc-2022Q4-base:1.1;
locks; strict;
comment	@// @;


1.2
date	2024.05.04.11.07.17;	author leot;	state Exp;
branches;
next	1.1;
commitid	GSivNew2yI8BJF8F;

1.1
date	2022.12.05.21.57.58;	author nikita;	state Exp;
branches;
next	;
commitid	WvEei8mXbsHGUp4E;


desc
@@


1.2
log
@git-crypt: Reference PR lib/58206

Seems exactly the same problem. Add a reference to it so once it is
addressed we can wait a couple of years and G/C this patch too.
@
text
@$NetBSD: patch-util.cpp,v 1.1 2022/12/05 21:57:58 nikita Exp $

Keep the C++ streams synchronized to the standard C streams on NetBSD otherwise
it is not possible to read via std::cin.

Related to PR lib/58206.

--- util.cpp.orig	2017-11-26 18:24:03.000000000 +0000
+++ util.cpp
@@@@ -141,7 +141,9 @@@@ static void	init_std_streams_platform ()
 void		init_std_streams ()
 {
 	// The following two lines are essential for achieving good performance:
+#ifndef __NetBSD__
 	std::ios_base::sync_with_stdio(false);
+#endif
 	std::cin.tie(0);
 
 	std::cin.exceptions(std::ios_base::badbit);
@


1.1
log
@security/git-crypt: Import git-crypt version 0.7.0 from wip.

git-crypt enables transparent encryption and decryption of files in a
git repository.  Files which you choose to protect are encrypted when
committed, and decrypted when checked out.  git-crypt lets you freely
share a repository containing a mix of public and private content.
git-crypt gracefully degrades, so developers without the secret key can
still clone and commit to a repository with encrypted files.  This lets
you store your secret material (such as keys or passwords) in the same
repository as your code, without requiring you to lock down your entire
repository.
@
text
@d1 1
a1 1
$NetBSD$
d6 1
a6 1
XXX: Why?
@