From: Sverre Rabbelier <srabbelier@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
gitster@pobox.com, git@vger.kernel.org,
Brandon Casey <drafnel@gmail.com>
Subject: Re: [PATCH] t/t7300: workaround ancient touch by rearranging arguments
Date: Sat, 18 Sep 2010 01:26:25 +0200 [thread overview]
Message-ID: <AANLkTinKxSugWedXxLPkSUKyRBBkTimawVY23+A5nzsZ@mail.gmail.com> (raw)
In-Reply-To: <20100916003117.GA2527@sigill.intra.peff.net>
Heya,
On Thu, Sep 16, 2010 at 02:31, Jeff King <peff@peff.net> wrote:
> Hmm, this seemed eerily familiar, and sure enough:
>
> http://article.gmane.org/gmane.comp.version-control.git/101270
Does this call for a git_touch which does a regular 'touch' for each
of its arguments?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-09-17 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 20:58 [PATCH] t/t7300: workaround ancient touch by rearranging arguments Brandon Casey
2010-09-15 22:08 ` Junio C Hamano
2010-09-16 0:31 ` Jeff King
2010-09-17 23:26 ` Sverre Rabbelier [this message]
2010-09-18 3:46 ` Jeff King
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=AANLkTinKxSugWedXxLPkSUKyRBBkTimawVY23+A5nzsZ@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=casey@nrlssc.navy.mil \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).