From: David Aguilar <davvid@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, gitster@pobox.com, markus.heidelberg@web.de,
jnareb@gmail.com, j.sixt@viscovery.net
Subject: Re: [PATCH v2 2/2] diff: generate prettier filenames when using GIT_EXTERNAL_DIFF
Date: Thu, 28 May 2009 14:30:49 -0700 [thread overview]
Message-ID: <20090528213049.GA55167@gmail.com> (raw)
In-Reply-To: <20090528174436.GA12723@coredump.intra.peff.net>
On Thu, May 28, 2009 at 01:44:36PM -0400, Jeff King wrote:
> On Wed, May 27, 2009 at 11:11:17PM -0700, David Aguilar wrote:
>
> > +int git_mkstemps(char *path, size_t n, const char *template, int suffix_len);
>
> FWIW, I find this name not very descriptive. From the name, I would
> expect it to do the exact same thing as mkstemps, but be our own
> personal implementation. But it is actually a wrapper that behaves
> somewhat differently. So I wonder if "mkstemps_tmpdir" or something
> would be a better name.
It does exactly what git_mkstemp() does, plus the extra
suffix_len parameter. If we rename this function we have to
rename both.
> Is there a reason _not_ to always just use the pretty filename? It looks
> like you turn it on for external diff, but off for textconv. I don't
> think there is a reason not to use it for textconv.
I was not aware of the other code paths and only wanted to
affect the one that I knew about. I agree that making that the
default behavior would be great, meaning we could drop the
pretty_filename flag altogether.
If you and others agree that the user-friendly names are a good
thing to have by default then I can rework patch 2/2.
> However, I suspect that all callers should use pretty filenames, and
> then this bit would just go away.
I fully agree.
--
David
next prev parent reply other threads:[~2009-05-28 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 6:11 [PATCH v2 1/2] compat: add a mkstemps() compatibility function David Aguilar
2009-05-28 6:11 ` [PATCH v2 2/2] diff: generate prettier filenames when using GIT_EXTERNAL_DIFF David Aguilar
2009-05-28 17:44 ` Jeff King
2009-05-28 21:30 ` David Aguilar [this message]
2009-05-28 22:06 ` Jeff King
2009-05-28 7:07 ` [PATCH v2 1/2] compat: add a mkstemps() compatibility function Johannes Sixt
2009-05-28 9:31 ` David Aguilar
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=20090528213049.GA55167@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jnareb@gmail.com \
--cc=markus.heidelberg@web.de \
--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).