I'm trying to make my git server sends http messages in non-ASCII
encoding. And I have a question.
At 206-218 in remote-curl.c:
static int show_http_message(struct strbuf *type, struct strbuf *charset,
struct strbuf *msg)
{
const char *p, *eol;
/*
* We only
- Written policy: https://git-scm.com/trademark
My browser shows an Untrusted Connection page when click the link.
Does git-scm have no TLS certificate?
--
View this message in context:
http://git.661346.n2.nabble.com/Git-SFC-Status-Update-tp7628669p7628850.html
Sent from the git mailing
On Wed, Apr 8, 2015 at 8:08 PM, Tony Finch d...@dotat.at wrote:
Yi, EungJun semtlen...@gmail.com wrote:
I want a way to response a remote message when a client send any kind
of request. Is it possible?
Yes, though you need a wrapper around git. Recent versions of gitolite
have a motd
Hello. I am serving a git hosting service for my company.
Sometimes I want to send a warning message to users who use my
service; e.g. the service will be shutdown tomorrow for a while
temporary.
I know it is possible to a remote message by hooks or HTTP body if an
error occured. But it seems
Some git hosting services, like Github, a url to a git repository can
be changed by changing the name of the repository by the owner. If
someone tries to get the repository with the old url, usually the
hosting service serves the request with the repository indiciated by
the new url. It is very
are mucking with code in the split_line function, we
change a '*' quantifier to a '+' quantifier when matching the $COLOR
expression which has the side effect of speeding everything up while
eliminating useless '' elements in the returned array.
Reported-by: Yi EungJun semtlen...@gmail.com
Signed
I timed this one versus the existing diff-highlight. It's about 7%
slower. That's not great, but is acceptable to me. The String::Multibyte
version was a lot faster, which was nice (but I'm still unclear on
_why_).
I think the reason is here:
sub split_line {
local $_ = shift;
From: Yi EungJun eungjun...@navercorp.com
Highlighted string might be broken if the common subsequence is a proper subset
of a multibyte character. For example, if the old string is 진 and the new
string is 지, then we expect the diff is rendered as follows:
-진
+지
but actually
I heard Git Contributors Summit is scheduled on April 8th at Git Merge 2015.
Does anyone know the agenda of the summit? I am considering to attend the
summit.
--
View this message in context:
http://git.661346.n2.nabble.com/ANNOUNCE-Git-Merge-April-8-9-Paris-tp7624561p7625750.html
Sent from
I'm very glad to hear that. Thanks to all reviewers!
On Thu, Jan 29, 2015 at 3:19 PM, Junio C Hamano gits...@pobox.com wrote:
Thanks; queued. Let's run with this and try to make it graduate
early next cycle.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en;q=0.9, *;q=0.1
LANGUAGE=ko LANG=en_US.UTF-8 - Accept
I agree that a list of char* is enough for language_tags.
Thanks for your review and patch. I'll apply your patch and send v9.
On Wed, Jan 28, 2015 at 3:15 PM, Junio C Hamano gits...@pobox.com wrote:
On Tue, Jan 27, 2015 at 3:34 PM, Junio C Hamano gits...@pobox.com wrote:
Yi EungJun semtlen
From: Yi EungJun eungjun...@navercorp.com
Change since v8
Apply Junio's patch: Use an array of char* instead of strbuf for language_tags.
Yi EungJun (1):
http: Add Accept-Language header if possible
http.c | 147 +
remote
From: Yi EungJun eungjun...@navercorp.com
Change since v7
From Torsten Bögershausen's review:
* remove unnecessary if-statement
From Eric Sunshine's review:
* fix memory leaks and uninitialized variables
* remove unnecessary if-statement
From Junio C Hamano's review
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en;q=0.9, *;q=0.1
LANGUAGE=ko LANG=en_US.UTF-8 - Accept
From: Yi EungJun eungjun...@navercorp.com
Changes since v6
From Junio C Hamano's review:
* Fix check_language() in t5550-http-fetch-dumb.sh as his suggestion.
From Eric Sunshine's review:
* Rewrite the parser without state.
Yi EungJun (1):
http: Add Accept-Language header if possible
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en;q=0.9, *;q=0.1
LANGUAGE=ko LANG=en_US.UTF-8 - Accept
Hello, all.
I just have started to develop SVNGit, the servlet library in pure
Java for SVN Client to checkout Git repository. The project is hosted
at https://github.com/naver/svngit.
Since the project is at very early stage, SVNGit unstably supports
only a few SVN commands: checkout, update
points
an empty string.
From Jeff King's advice:
* get_preferred_languages() considers LC_MESSAGES only if NO_GETTEXT is not
defined.
* Remove the tests for LC_MESSAGES, LANG and LC_ALL.
Yi EungJun (1):
http: Add Accept-Language header if possible
http.c | 173
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en;q=0.9, *;q=0.1
LANGUAGE=ko LANG=en_US.UTF-8 - Accept
Could you tell me your locale information from executing 'locale'
command and the verbose message you can get by accessing any git
repository via HTTP protocol? (e.g. GIT_CURL_VERBOSE=1 git clone
http://github.com/foo/bar )
I think the failures are related with your locale information.
On Sat,
Thank you for providing useful information to fix the failures.
On Sun, Dec 7, 2014 at 6:04 AM, Torsten Bögershausen tbo...@web.de wrote:
On 2014-12-06 20.44, Yi, EungJun wrote:
Could you tell me your locale information from executing 'locale'
command and the verbose message you can get
Changes since v4
* Fix styles as Junio C Hamano suggested.
* Limit number of languages and length of Accept-Language header.
Yi EungJun (1):
http: Add Accept-Language header if possible
http.c | 154 +
remote-curl.c
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en;q=0.9, *;q=0.1
LANGUAGE=ko LANG=en_US.UTF-8 - Accept
Thanks very much for your detailed review and sorry for late reply.
2014-07-22 4:01 GMT+09:00 Junio C Hamano gits...@pobox.com:
Yi EungJun semtlen...@gmail.com writes:
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages
Changes since v3:
* Fix styles and syntax. (Thanks to Jeff King and Eric Sunshine)
* Cache Accept-Language header. (Thanks to Jeff King)
* Remove floating point numbers. (Thanks to Junio C Hamano)
* Make the for-loop to get the value of the header simpler.
* Add more comments.
Yi EungJun (1
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en; q=0.9, *; q=0.1
LANGUAGE=ko LANG=en_US.UTF-8
2014-07-13 13:26 GMT+09:00 Eric Sunshine sunsh...@sunshineco.com:
+ /* Decide the precision for q-factor on number of preferred
languages. */
+ if (num_langs + 1 100) { /* +1 is for '*' */
+ q_precision = 0.001;
+ q_format = ; q=%.3f;
+ } else
2014-07-14 1:57 GMT+09:00 Junio C Hamano gits...@pobox.com:
If you do not want floating point (and I think we tend to avoid it
when we do not need it), you can realize that in your use of 0.1
and 0.01 and 0.001 there is nothing fundamentally floating-point;
you can measure how many digits
Thanks for your detailed review and nice suggestions. I will accept
most of them.
2014-07-12 2:35 GMT+09:00 Jeff King p...@peff.net:
+ /* Decide the precision for q-factor on number of preferred languages.
*/
+ if (num_langs + 1 100) { /* +1 is for '*' */
+ q_precision =
2014-07-09 19:40 GMT+09:00 Peter Krefting pe...@softwolves.pp.se:
Yi EungJun:
Example:
LANGUAGE= -
LANGUAGE=ko - Accept-Language: ko; q=1.000, *; q=0.001
LANGUAGE=ko:en - Accept-Language: ko; q=1.000, en; q=0.999, *; q=0.001
Avoid adding q=1.000. It is redundant (the default for any
2014-07-11 5:10 GMT+09:00 Jeff King p...@peff.net:
On Wed, Jul 09, 2014 at 11:46:14AM +0100, Peter Krefting wrote:
Jeff King:
I did some digging, and I think the public API is setlocale with a NULL
parameter, like:
printf(%s\n, setlocale(LC_MESSAGES, NULL));
That still will end up
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by $LANGUAGE, $LC_ALL, $LC_MESSAGES and $LANG.
Examples:
LANGUAGE= -
LANGUAGE=ko:en - Accept-Language: ko, en; q=0.9, *; q=0.1
LANGUAGE=ko LANG=en_US.UTF-8
2014-07-12 1:24 GMT+09:00 Eric Sunshine sunsh...@sunshineco.com:
On Fri, Jul 11, 2014 at 5:22 AM, Yi, EungJun semtlen...@gmail.com wrote:
2014-07-09 6:52 GMT+09:00 Eric Sunshine sunsh...@sunshineco.com:
+ grep ^Accept-Language: ko; q=1.000, en; q=0.999, \*; q=0.001
actual
Do you want
=en_US.UTF-8 - Accept-Language: en-US, *; q=0.1
This gives git servers a chance to display remote error messages in
the user's preferred language.
Signed-off-by: Yi EungJun eungjun...@navercorp.com
---
http.c | 125 +
remote-curl.c
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by 'LANGUAGE' environment variable if the variable is
not empty.
Example:
LANGUAGE= -
LANGUAGE=ko - Accept-Language: ko; q=1.000, *; q=0.001
LANGUAGE=ko:en
2014-07-09 14:10 GMT+09:00 Jeff King p...@peff.net:
On Wed, Jul 09, 2014 at 12:54:06AM +0900, Yi EungJun wrote:
From: Yi EungJun eungjun...@navercorp.com
Add an Accept-Language header which indicates the user's preferred
languages defined by 'LANGUAGE' environment variable if the variable
From: Yi EungJun eungjun...@navercorp.com
extract_content_type() could not extract a charset parameter if the
parameter is not the first one and there is a whitespace and a following
semicolon just before the parameter. For example:
text/plain; format=fixed ;charset=utf-8
And it also could
From: Yi EungJun eungjun...@navercorp.com
extract_content_type() could not extract a charset parameter if the
parameter is not the first one and there is a whitespace and a following
semicolon just before the parameter. For example:
text/plain; format=fixed ;charset=utf-8
And it also could
Thanks for your advice. i'll resend it.
2014-06-17 3:26 GMT+09:00 Junio C Hamano gits...@pobox.com:
Yi EungJun semtlen...@gmail.com writes:
Could you change the author to Yi EungJun eungjun...@navercorp.com
if you apply this patch?
You can send a patch with the desired From: line
From: Yi EungJun eungjun...@navercorp.com
Signed-off-by: Yi EungJun eungjun...@navercorp.com
---
Documentation/technical/http-protocol.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/http-protocol.txt
b/Documentation/technical/http-protocol.txt
Could you change the author to Yi EungJun eungjun...@navercorp.com
if you apply this patch?
--
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
Could you change the author to Yi EungJun eungjun...@navercorp.com
if you apply this patch?
--
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
Maybe. But I would worry somewhat about sites which provide a useless
and verbose text/plain message. Ideally an x-git-error-message would be
no more than few lines, suitable for the error message of a terminal
program. I would not want a site-branded Your page cannot be found.
Here's a
Currently, if user tried to access a git repository via HTTP and it
fails because the user's permission is not enough to access the
repository, git client tells that http request failed and the error
was 403 forbidden.
But It is not enough for user to understand why it fails, especially
if the
a32b84ed7cec5686e43a47195dfa8114f83619f3 (2/2)
Ref 'refs/heads/master' was rewritten
~/filter-branch2$ git log -- b
commit 19611f9eaf412232e237afcc059d0324a862062f
Author: Yi EungJun semtlen...@gmail.com
Date: Tue Sep 18 23:51:53 2012 +0900
first
Am I doing something wrong?
On Mon, Sep 17, 2012 at 2:06 AM, Andreas
I think it should be '... git reset -q $GIT_COMMIT -- filename'
It works! Thanks to Hannes and Andreas!
On Wed, Sep 19, 2012 at 12:10 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 9/18/2012 17:01, schrieb Yi, EungJun:
--index-filter git rm --cached -qr -- . git reset -q -- filename
Hmm
Thanks for your help, Jan!
On Sat, Sep 15, 2012 at 10:26 PM, Jan Engelhardt jeng...@inai.de wrote:
On Saturday 2012-09-15 15:24, Yi, EungJun wrote:
bee-lob or bla:b?
http://en.wiktionary.org/wiki/blob
BLOB as a Binary Large OBject reeks of a retronym.
I guess bee-lob is correct if it means
48 matches
Mail list logo
