From: Junio C Hamano <gitster@pobox.com>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: <git@vger.kernel.org>
Subject: Re: Make patch-id more flexible?
Date: Fri, 24 Nov 2017 16:51:06 +0900 [thread overview]
Message-ID: <xmqqlgiwm7x1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171124073327.GA15188@vmlxhi-102.adit-jv.com> (Eugeniu Rosca's message of "Fri, 24 Nov 2017 08:33:27 +0100")
Eugeniu Rosca <erosca@de.adit-jv.com> writes:
> file-names. Here comes my actual question. Would it be conceptually fine
> to implement some `git patch-id` parameter, which would allow ignoring
> the file-names (or reducing those to their `basename`) before computing
> the patch id? Or would it break the concept of patch id (which shouldn't
> accept variations)?
My gut feeling is that a tool like that would be fine as long as it
is local to your organization and is not called "git patch-id"; it
may be useful in the situation you described, but as you mention
above, it feels that it is differnt from what a patch-id is.
next prev parent reply other threads:[~2017-11-24 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 7:33 Make patch-id more flexible? Eugeniu Rosca
2017-11-24 7:51 ` Junio C Hamano [this message]
2017-11-30 10:35 ` Eugeniu Rosca
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlgiwm7x1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=erosca@de.adit-jv.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).