git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Carlos Rica <jasampler@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] mktag.c: improve verification of tagger field and tests
Date: Wed, 26 Mar 2008 09:45:01 -0700	[thread overview]
Message-ID: <7vhcete8oi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47EA7927.9060201@nrlssc.navy.mil> (Brandon Casey's message of "Wed, 26 Mar 2008 11:26:15 -0500")

Brandon Casey <casey@nrlssc.navy.mil> writes:

> Eventually filter-branch along with the rest of git will be rewritten
> in c and the need for many low-level git tools will vanish.

That holds true only for the tools shipped with git.git itself.  However,
you never should forget that people _script_ around git.  I do not see a
reason to stop supporting mktag in this discussion.

I would suggest:

 * make mktag.c a built-in first;

 * rename verify_tag() in mktag.c to verify_tag_buffer(), and update its
   implementation to tighten the format validation, perhaps along the
   lines you propose in your patch, and move it to tag.c.  By the way, I
   think tagger information should get the same validation as committer
   and author information gets elsewhere in the system;

 * add a call to verify_tag_buffer() you introduce above immediately
   before write_sha1_file() in builtin-tag.c, to make sure both programs
   produce valid tags, with the same definition of validity.

  parent reply	other threads:[~2008-03-26 16:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1206490795-13247-1-git-send-email-casey@nrlssc.navy.mil>
2008-03-26  0:40 ` [PATCH] mktag.c: improve verification of tagger field and tests Brandon Casey
2008-03-26  0:44   ` Brandon Casey
2008-03-26 11:21   ` Carlos Rica
2008-03-26 16:26     ` Brandon Casey
2008-03-26 16:37       ` Brandon Casey
2008-03-26 16:45       ` Junio C Hamano [this message]
2008-03-26 21:03         ` Brandon Casey
2008-03-27 16:16           ` [PATCH v2] " Brandon Casey
2008-03-31  8:40             ` Junio C Hamano
2008-03-31 16:04               ` Brandon Casey
2008-03-31 23:25                 ` [PATCH] mktag.c: tweak validation of tagger field and adjust test script Brandon Casey
2008-04-01  5:39                   ` Junio C Hamano

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=7vhcete8oi.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    --cc=jasampler@gmail.com \
    /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).