From: "Hannes Eder" <hannes@hanneseder.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Catalin Marinas" <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: [STGIT][PATCH] new: translate non word characters in patch name to '-'
Date: Wed, 31 Dec 2008 09:07:51 +0100 [thread overview]
Message-ID: <154e089b0812310007j6642af70v4bfd64b784da8b4c@mail.gmail.com> (raw)
In-Reply-To: <20081229212119.GA3015@diana.vm.bytemark.co.uk>
On Mon, Dec 29, 2008 at 10:21 PM, Karl Hasselström <kha@treskal.com> wrote:
> On 2008-12-29 21:15:44 +0100, Hannes Eder wrote:
>
>> What about instead of 'fail with an informative message', just issue
>> a warning that the name has been mangled. I use pathnames in patch
>> names frequently, so this would be very handy.
>
> Hmm, I'm still skeptical. Programs that try to be too clever all too
> often end up just being annoying and unpredictable.
>
>> I guess some with with more python skills needs to clean that up,
>> this is the first stuff I do in python ;).
>
> The code looks OK -- but as I said, I don't agree with what it's
> trying to do.
>
> There's a small inconsistency: you fail if the name contains "..", but
> correct single bad characters.
".." is used to denote patch name ranges [<patch1>..<patch2>] for
commands like "stg pop", "stg push", and so forth, therefore I think
it is wise to exclude ".." from single patch names [<patch3>].
> And as I recall, stgit.namelength is about the automatically generated
> patch names -- there's no limit for the names provided by the user.
Ok.
Maybe we should start defining what a 'valid' patch name has to look
like, i.e. define
def is_patch_name_valid(patchname)
Best,
Hannes
next prev parent reply other threads:[~2008-12-31 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 12:37 [STGIT][PATCH] new: translate non word characters in patch name to '-' Hannes Eder
2008-12-28 20:49 ` Karl Hasselström
2008-12-29 20:15 ` Hannes Eder
2008-12-29 21:21 ` Karl Hasselström
2008-12-31 8:07 ` Hannes Eder [this message]
2008-12-31 10:38 ` Karl Hasselström
2009-01-15 14:53 ` David Kågedal
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=154e089b0812310007j6642af70v4bfd64b784da8b4c@mail.gmail.com \
--to=hannes@hanneseder.net \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).