On Sat, Jun 29, 2013 at 07:13:40PM -0700, Junio C Hamano wrote:
> "brian m. carlson" writes:
> Does this correspond to the following comment in the same file, and
> if so, shouldn't this part of your patch?
Yes, yes, it should.
> We used to allow te original up-to-6 form and this update is about
"brian m. carlson" writes:
> The commit code already contains code for validating UTF-8, but it
> does not check for invalid values, such as guaranteed
> non-characters and surrogates. Fix this by explicitly checking
> for and rejecting such characters.
>
> Signed-off-by: brian m. carlson
> ---
Thanks, both. Will queue.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
"W. Trevor King" writes:
> On Sat, Jun 22, 2013 at 10:46:23AM -0400, W. Trevor King wrote:
>> David and Junio mentioned that I'd missed a few 2.6 references in my
>> initial pass. Here's a second attempt that does some deeper
>> reworking of the effected sections.
>
> No comments after a week, s
On Sat, Jun 22, 2013 at 10:46:23AM -0400, W. Trevor King wrote:
> David and Junio mentioned that I'd missed a few 2.6 references in my
> initial pass. Here's a second attempt that does some deeper
> reworking of the effected sections.
No comments after a week, so I'm giving this patch series a bu
The commit code accepts pseudo-UTF-8 sequences that encode a character with more
bytes than necessary. Reject such sequences, since they are not valid UTF-8.
Signed-off-by: brian m. carlson
---
commit.c | 14 --
t/t3900-i18n-commit.sh | 8
t/t3900/UTF
The commit code already contains code for validating UTF-8, but it does not
check for invalid values, such as guaranteed non-characters and surrogates. Fix
this by explicitly checking for and rejecting such characters.
Signed-off-by: brian m. carlson
---
commit.c | 18 +
This series contains a pair of patches that improve the validation of
the UTF-8 used in commit messages. Invalid codepoints, such as
surrogates and guaranteed non-characters, are rejected, along with
overlong UTF-8 sequences.
brian m. carlson (2):
commit: reject invalid UTF-8 codepoints
commi
I will like to discuss a very important oil project with you. I wrote to know
if this is your valid email.Please, email me for details on:
hyuklee5...@gmail.com
Lee.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More
Thomas Gummerer writes:
> ae75342 test-lib: rearrange start/end of test_expect_* and test_skip
> changed the way tests are started/stopped, but did not update the perf
> tests. They were therefore giving the wrong output, because of the
> wrong test count. Fix this by starting and stopping the
ae75342 test-lib: rearrange start/end of test_expect_* and test_skip
changed the way tests are started/stopped, but did not update the perf
tests. They were therefore giving the wrong output, because of the
wrong test count. Fix this by starting and stopping the tests
correctly.
Signed-off-by: T
> GIT_ROOT_DIR=../../..
> GIT_EXEC_PATH=$(cd "$(dirname "$0")" && cd ${GIT_ROOT_DIR} && pwd)
> GIT_MEDIAWIKI="$GIT_EXEC_PATH"/contrib/mw-to-git
> PATH="$GIT_MEDIAWIKI"/contrib/mw-to-git:"$PATH"
> GPLEXTRA="$GIT_MEDIAWIKI"/contrib/mw-to-git
>
> exec "${GIT_EXEC_PATH}/bin-wrappers/git" "$@"
Should I
On 28/06/13 22:42, Fredrik Gustafsson wrote:
> Hi,
>
> On Fri, Jun 28, 2013 at 09:53:10PM +1200, Chris Packham wrote:
>> This allows the user some finer grained control over how the update is
>> done. The primary motivation for this was interoperability with stgit
>> however being able to intercep
13 matches
Mail list logo
