From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7912 invoked by alias); 12 Dec 2019 02:36:13 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 7874 invoked by uid 89); 12 Dec 2019 02:36:13 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-HELO:sk:mail-qk, HX-Languages-Length:733, H*r:TLS1 X-HELO: mail-qk1-f175.google.com Received: from mail-qk1-f175.google.com (HELO mail-qk1-f175.google.com) (209.85.222.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 12 Dec 2019 02:36:11 +0000 Received: by mail-qk1-f175.google.com with SMTP id x1so359583qkl.12 for ; Wed, 11 Dec 2019 18:36:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=TVQgpMjQSDT8l9tVmV0YdHUiQDuOExdOBsfiXjCTTE4=; b=vHdGrD9hJ8who3Fxgg+H58CT5/1IsDTJZOlXy+pre5Lk8EbRNi8OY7GqXwyv3gDXxc icm1LJIKI7zS5gVAwX7AYEZnX5sRmQ5Od/MzlTkBFau6pBi73iDi3BJaPpZC1V7r0AX9 iXcIAfLezcJGs/Q06cQXOiXKBp8K0lMvwAJYSwWnm8e9IzfiK2KB/gTbYJeWpocqJXIq HyKCEeOMPDwdMRZcwABtOtrR43sTr0LggFNSUEQ88YXQtn3hmP30PODVkufXtxAelmtC e5HPz6h7ywQu7orBt8y24AKF0CW7it5MO8KA0Lc+LX0brY1fKAie3jr5zAmJtb+YGFNH FlFw== Return-Path: Received: from [192.168.1.127] ([192.222.216.4]) by smtp.gmail.com with ESMTPSA id 2sm1298140qkv.98.2019.12.11.18.36.08 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 11 Dec 2019 18:36:08 -0800 (PST) From: Philippe Blain Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Add script to setup codesigning on macOS Message-Id: <4CFCAA53-2233-4013-A682-48BB2025058E@gmail.com> Date: Thu, 12 Dec 2019 02:36:00 -0000 To: gdb@sourceware.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-SW-Source: 2019-12/txt/msg00012.txt.bz2 Hello,=20 I=E2=80=99m interested in setting up a macOS build of GDB on conda-forge ([= 1], [2]) and it seems that in order to do it the codesigning procedure woul= d have to be automated, i.e. entirely command-line driven.=20 The LLDB project already has a script doing exactly that [3], and I was thi= nking of adding such a script to the conda-forge GDB feedstock.=20 However, I thought it could be a good idea to add it directly to the GDB re= pository. Would a patch adding such a script be well received ? Thanks, Philippe Blain. [1] https://conda-forge.org [2] https://github.com/conda-forge/gdb-feedstock/issues/7 [3] https://github.com/llvm/llvm-project/blob/master/lldb/scripts/macos-set= up-codesign.sh >From gdb-return-47330-listarch-gdb=sources.redhat.com@sourceware.org Thu Dec 12 06:17:31 2019 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 89410 invoked by alias); 12 Dec 2019 06:17:30 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Delivered-To: mailing list gdb@sourceware.org Received: (qmail 89401 invoked by uid 89); 12 Dec 2019 06:17:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=investigations, H*MI:sk:838snjb, HX-Languages-Length:1149 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 12 Dec 2019 06:17:29 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:60467) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ifHmw-00012L-5b; Thu, 12 Dec 2019 01:17:26 -0500 Received: from [176.228.60.248] (port=4552 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1ifHmv-00018P-NT; Thu, 12 Dec 2019 01:17:25 -0500 Date: Thu, 12 Dec 2019 06:17:00 -0000 Message-Id: <838sni9ifm.fsf@gnu.org> From: Eli Zaretskii To: Christian Biesinger CC: gdb@sourceware.org, palves@redhat.com In-reply-to: (message from Christian Biesinger on Wed, 11 Dec 2019 17:59:39 -0500) Subject: Re: Renaming .c files to .cc? References: <838snjbkqm.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00013.txt.bz2 Content-length: 1126 > From: Christian Biesinger > Date: Wed, 11 Dec 2019 17:59:39 -0500 > Cc: gdb@sourceware.org, Pedro Alves > > > Not every Git command has a --follow option, so renaming files does > > have disadvantages in that area. > > Do you have a specific command in mind that doesn't? I haven't come > across that yet myself. Are you saying that every Git command supports that option? I don't think so. And even those who do support it impose limitations when it's used. For example, $ git log file1 file2 ... works, but $ git log --follow file1 file2 ... fails with an error message. So many important forensic investigations limit you to single files when using --follow. > > Also, even with --follow, Git's tracking of renaming is heuristics, > > so it can fail. > > Technically correct, but not an issue in practice when files are being > renamed without changes, like they would be here. That's not guaranteed, because several files with similar contents can dupe the heuristics. Anyway, like Pedro said: the reasons for being in the "rather not" camp are not strong.