From: Tom Tromey <tromey@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: overseers@sources.redhat.com
Subject: Re: commit_prep perl question
Date: Tue, 29 Jul 2003 21:01:00 -0000 [thread overview]
Message-ID: <87isplukf0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20030729205700.GA23614@disaster.jaj.com>
Phil> 1) How do I test changes to commit_prep before presenting them
Phil> for approval?
Make a dummy repository somewhere and try it there.
Phil> 2) In the generalized commit_prep, there is basically this code:
Phil> [ ... ]
Looks like a bug to me. I didn't look at the code, just your
extraction.
Tom
prev parent reply other threads:[~2003-07-29 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 20:57 Phil Edwards
2003-07-29 21:01 ` Tom Tromey [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=87isplukf0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=overseers@sources.redhat.com \
--cc=phil@jaj.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 read-only IMAP folder(s) and NNTP newsgroup(s).