git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Samium Gromoff <_deepfire@feelingofgreen.ru>
Cc: git@vger.kernel.org
Subject: Re: Git-tag's over-aggressive pipework fails badly on fresh Ubuntu, over NFS.
Date: Wed, 26 Sep 2007 00:01:18 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709260000340.28395@racer.site> (raw)
In-Reply-To: <87hclifk7i.wl@betelheise.deep.net>

Hi,

On Wed, 26 Sep 2007, Samium Gromoff wrote:

> Without the following applied, git-tag -s gets zeroes into TAG_TMP
> in place of the .asc sig, resulting in an unsigned commit.

You'll be delighted to hear that it is no longer necessary to patch 
git-tag.sh (git-tag is not the right place), since git-tag is now a 
builtin (without much in the way of pipes...)

Ciao,
Dscho

      reply	other threads:[~2007-09-25 23:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 22:34 Git-tag's over-aggressive pipework fails badly on fresh Ubuntu, over NFS Samium Gromoff
2007-09-25 23:01 ` Johannes Schindelin [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0709260000340.28395@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=_deepfire@feelingofgreen.ru \
    --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. 
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 NNTP newsgroup(s).