From: David Aguilar <davvid@gmail.com>
To: Markus Heidelberg <markus.heidelberg@web.de>
Cc: git@vger.kernel.org, gitster@pobox.com,
johannes.schindelin@gmx.de, nick@incise.org
Subject: Re: [PATCH v3] diff: generate prettier filenames when using GIT_EXTERNAL_DIFF
Date: Tue, 26 May 2009 13:52:31 -0700 [thread overview]
Message-ID: <20090526205230.GA66544@gmail.com> (raw)
In-Reply-To: <200905262231.50892.markus.heidelberg@web.de>
On Tue, May 26, 2009 at 10:31:50PM +0200, Markus Heidelberg wrote:
> David Aguilar, 26.05.2009:
> > Diffing "name.ext" now generates "name.XXXX.ext".
> > Diffing files with no extension now generates "name_XXXX".
>
> Would it simplify the patch when using "name_XXXX.ext" and "name_XXXX"?
> Or what about "XXXX_name.ext" and "XXXX_name"? Then you don't even have
> to search for the dot and it has the advantage to show the original
> filename without some random letters in the middle of it.
>
> Markus
>
In that case suffix_len is always len(basename) + 1
and there's less strbuf juggling to do.
That is simpler. Let's do that.
My next patch series will be two parts:
part 1: add compat/mkstemps.c
part 2: use it in prep_temp_blob() via git_mkstemps()
Part 1 has me a little nervous because I'm not sure which
platforms in the Makefile need the
NO_MKSTEMPS = YesPlease
setting. I only have access to mac + linux, so I can do the
right thing there, but I'll have to make a best guess for the
rest of the platforms.
Perhaps the best answer is to set them all to YesPlease except
for mac and openbsd, which I know have native implementations.
--
David
next prev parent reply other threads:[~2009-05-26 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 5:36 [PATCH v3] diff: generate prettier filenames when using GIT_EXTERNAL_DIFF David Aguilar
2009-05-26 6:01 ` Stephen Boyd
2009-05-26 17:37 ` David Aguilar
2009-05-26 6:12 ` Junio C Hamano
2009-05-26 20:31 ` Markus Heidelberg
2009-05-26 20:52 ` David Aguilar [this message]
2009-05-26 21:41 ` 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=20090526205230.GA66544@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=markus.heidelberg@web.de \
--cc=nick@incise.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.