From: Pierre Habouzit <madcoder@debian•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: torvalds@linux-foundation•org, git@vger•kernel.org
Subject: Re: [PATCH 2/5] Update git-sh-setup(1) to allow transparent use of git-rev-parse --parseopt
Date: Sun, 04 Nov 2007 10:14:49 +0100 [thread overview]
Message-ID: <20071104091449.GC26269@artemis.corp> (raw)
In-Reply-To: <7vd4uqtpza.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Sun, Nov 04, 2007 at 07:43:53AM +0000, Junio C Hamano wrote:
> Trust me that this kind of backdoor, especially when the
> intended uses of the backdoor is not documented well, will be
> abused by (perhaps clueless, perhaps curious, perhaps fearless)
> users and you will get blamed.
That has been fixed, and documented in git-sh-setup. I renumbered my 3
patches incorrectly though. Those are supposed to supersede patches 2, 4, and 9.
Cheers,
--
·O· Pierre Habouzit
··O madcoder@debian•org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-04 9:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 22:39 let's retry this based on git-rev-parse --parseopt Pierre Habouzit
2007-11-02 22:39 ` [PATCH 1/5] Add a parseopt mode to git-rev-parse to bring parse-options to shell scripts Pierre Habouzit
2007-11-02 22:39 ` [PATCH 2/5] Update git-sh-setup(1) to allow transparent use of git-rev-parse --parseopt Pierre Habouzit
2007-11-02 22:39 ` [PATCH 3/5] Migrate git-clean.sh to use " Pierre Habouzit
2007-11-02 22:39 ` [PATCH 4/5] Migrate git-clone " Pierre Habouzit
2007-11-02 22:39 ` [PATCH 5/5] Migrate git-am.sh " Pierre Habouzit
2007-11-03 9:55 ` Alex Riesen
2007-11-03 11:54 ` Pierre Habouzit
2007-11-03 12:05 ` Pierre Habouzit
2007-11-03 17:50 ` [PATCH 5/5 FIX SPACING] " Pierre Habouzit
2007-11-03 17:50 ` [PATCH 6/5] Migrate git-merge.sh " Pierre Habouzit
2007-11-03 17:50 ` [PATCH 8/5] Migrate git-instaweb.sh " Pierre Habouzit
2007-11-03 17:50 ` [PATCH 9/5] Migrate git-checkout.sh to use git-rev-parse --parseopt --keep-dashdash Pierre Habouzit
2007-11-03 17:50 ` [PATCH 10/5] Migrate git-quiltimport.sh to use git-rev-parse --parseopt Pierre Habouzit
2007-11-03 18:35 ` [PATCH 11/5] Migrate git-repack.sh " Pierre Habouzit
2007-11-04 7:44 ` [PATCH 9/5] Migrate git-checkout.sh to use git-rev-parse --parseopt --keep-dashdash Junio C Hamano
2007-11-04 9:03 ` Pierre Habouzit
2007-11-04 13:48 ` Johannes Schindelin
2007-11-04 14:18 ` Pierre Habouzit
2007-11-04 7:43 ` [PATCH 2/5] Update git-sh-setup(1) to allow transparent use of git-rev-parse --parseopt Junio C Hamano
2007-11-04 9:11 ` [UPDATED PATCH 3/5] " Pierre Habouzit
2007-11-04 9:11 ` [UPDATED PATCH 5/5] Migrate git-clone to use " Pierre Habouzit
2007-11-04 9:11 ` [UPDATED PATCH 9/5] Migrate git-checkout.sh to use git-rev-parse --parseopt --keep-dashdash Pierre Habouzit
2007-11-04 9:14 ` Pierre Habouzit [this message]
2007-11-04 9:15 ` [PATCH 2/5] Update git-sh-setup(1) to allow transparent use of git-rev-parse --parseopt Pierre Habouzit
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=20071104091449.GC26269@artemis.corp \
--to=madcoder@debian$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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