Re: [PATCH v2] subtree: fix add and pull for GPG-signed commits

On Fri, Feb 23, 2018 at 5:45 PM, Junio C Hamano <gits...@pobox.com> wrote: > Stephen R Guglielmo <srguglie...@gmail.com> writes: > >> If log.showsignature is true (or --show-signature is passed) while >> performing a `subtree add` or `subtree pull`, the command f

[PATCH v2] subtree: fix add and pull for GPG-signed commits

. This commit fixes the issue by adding --no-show-signature to `log` calls in a few places, as well as using the more appropriate `rev-parse` instead where possible. Signed-off-by: Stephen R Guglielmo <s...@guglielmo.us> --- contrib/subtree/git-subtree.sh | 12 ++-- 1 file changed, 6 insertions

[PATCH] subtree: hide GPG signatures in calls to log

This fixes `add` and `pull` for GPG signed objects. Signed-off-by: Stephen R Guglielmo <s...@guglielmo.us> --- contrib/subtree/git-subtree.sh | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/contrib/subtree/git-subtree.sh b/contrib/subtree/git-subtree.sh

Re: Automatic parameters completion

On Thu, Feb 8, 2018 at 9:03 AM, Andrzej wrote: > I have Linux Mint and its terminal besides usual completion (add file name > when type first letter and press tab) also can complete git parameters. How > is doing this? Bash knows git or bash has special interface to

Re: Bug Report: Subtrees and GPG Signed Commits

On Mon, Feb 5, 2018 at 1:45 PM, Junio C Hamano wrote: > Given that all references to this shell function seem to do > > sometree=$(toptree_for_commit $something) > > and then $sometree is used as if it were a tree object name, I can > understand why the lack of

Re: Bug Report: Subtrees and GPG Signed Commits

On Mon, Feb 5, 2018 at 9:30 AM, Stephen R Guglielmo <srguglie...@gmail.com> wrote: > On Wed, Jan 31, 2018 at 7:33 AM, Stephen R Guglielmo > <srguglie...@gmail.com> wrote: >> On Tue, Jan 30, 2018 at 6:37 PM, Avery Pennarun <apenw...@gmail.com> wrote: >>> O

Re: Bug Report: Subtrees and GPG Signed Commits

On Wed, Jan 31, 2018 at 7:33 AM, Stephen R Guglielmo <srguglie...@gmail.com> wrote: > On Tue, Jan 30, 2018 at 6:37 PM, Avery Pennarun <apenw...@gmail.com> wrote: >> On Tue, Jan 30, 2018 at 6:24 PM, Junio C Hamano <gits...@pobox.com> wrote: >>> Stefa

Re: Bug Report: Subtrees and GPG Signed Commits

On Tue, Jan 30, 2018 at 6:37 PM, Avery Pennarun wrote: > On Tue, Jan 30, 2018 at 6:24 PM, Junio C Hamano wrote: >> Stefan Beller writes: >>> There has not been feedback for a while on this thread. >>> I think that is because subtrees

Re: Bug Report: Subtrees and GPG Signed Commits

Guglielmo <srguglie...@gmail.com> wrote: > Hi, just following up on this bug report. I have not heard back. Is > there additional information that's needed? Is there a better place to > file bug reports? > > Thanks > > On Sat, Jan 6, 2018 at 5:45 PM, Stephen R Guglielmo >

Re: Bug Report: Subtrees and GPG Signed Commits

Hi, just following up on this bug report. I have not heard back. Is there additional information that's needed? Is there a better place to file bug reports? Thanks On Sat, Jan 6, 2018 at 5:45 PM, Stephen R Guglielmo <srguglie...@gmail.com> wrote: > Hi all, > > I've noticed an

Bug Report: Subtrees and GPG Signed Commits

Hi all, I've noticed an issue regarding the use of `git subtree add` and `git subtree pull` when the subtree repository's commit (either HEAD or whatever commit specified by the subtree command) is signed with GPG. It seems to work properly if the commit is not signed but previous commits are.