On 07.10.18 13:36, Beat Bolli wrote:
> On 02.10.18 22:18, Jacob Keller wrote:
>> On Tue, Oct 2, 2018 at 1:07 PM Jacob Keller wrote:
>>>
>>> From: Jacob Keller
>>>
>>> make coccicheck is used in order to apply coccinelle semantic patches,
>>&
On 02.10.18 22:18, Jacob Keller wrote:
> On Tue, Oct 2, 2018 at 1:07 PM Jacob Keller wrote:
>>
>> From: Jacob Keller
>>
>> make coccicheck is used in order to apply coccinelle semantic patches,
>> and see if any of the transformations found within contrib/coccinelle/
>> can be applied to the
n Nieder
Signed-off-by: Beat Bolli
---
packfile.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/packfile.h b/packfile.h
index 51383774ec72..28318c5c7c42 100644
--- a/packfile.h
+++ b/packfile.h
@@ -1,12 +1,12 @@
#ifndef PACKFILE_H
#define PACKFILE_H
+#include "cac
to include this in the next
version of the cc/remote-odb topic.
Beat Bolli (1):
packfile: drop a repeated enum declaration
packfile.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.18.0
On 25.07.18 18:57, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> In the interest of code hygiene, make it easier to compile Git with the
>> flag -pedantic.
>>
>> Pure pedantic compilation with GCC 7.3 results in one warning per use of
>> the translation
Hi Jonathan
On 24.07.18 23:59, Jonathan Nieder wrote:
> Hi,
>
> Beat Bolli wrote:
>
>> When compiling under Apple LLVM version 9.1.0 (clang-902.0.39.2) with
>> "make DEVELOPER=1 DEVOPTS=pedantic", the compiler says
>>
>> remote-odb.c:87
Following up on my previous series bb/pedantic for gcc, here are two
fixes for pedantic compilation under MacOS 10.13.6 (High Sierra) with
the command line tools of Xcode Version 9.4.1 (9F2000).
Beat Bolli (2):
packfile: drop a repeated enum declaration
remote-odb: un-inline function
e]
Remove the inline specifier that would only make sense if
remote_odb_reinit were defined in the header file. Moving it into the
header is not possible because the called function remote_odb_do_init is
static and thus not visible from the includers of the header.
Signed-off-by: Beat Bolli
---
remote
including packfile.h.
Signed-off-by: Beat Bolli
---
packfile.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/packfile.h b/packfile.h
index 51383774ec72..9b6198c4c7e0 100644
--- a/packfile.h
+++ b/packfile.h
@@ -6,7 +6,6 @@
/* in object-store.h */
struct packed_git;
struct object_inf
the parenthesising of i18n strings with
-DUSE_PARENS_AROUND_GETTEXT_N=0.
Signed-off-by: Beat Bolli
---
Now with -DUSE_PARENS_AROUND_GETTEXT_N=0 instead of =No.
This is the convenience knob for all developers that led to the series
bb/pedantic[1]. It does not depend on this series, though.
[1] https
On 24.07.18 20:50, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> On 24.07.18 20:22, Junio C Hamano wrote:
>>
>>>> This was already fixed (differently) in
>>>> <20180705183445.30901-1-dev+...@drbeat.li>.
>>>
>>> Thanks
On 24.07.18 20:22, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> Hi Jeff
>>
>> On 24.07.18 17:30, g...@jeffhostetler.com wrote:
>>> From: Jeff Hostetler
>>>
>>> In commit fb0dc3bac135e9f6243bd6d293e8c9293c73b9cd code was added
>>>
Hi Jeff
On 24.07.18 17:30, g...@jeffhostetler.com wrote:
> From: Jeff Hostetler
>
> In commit fb0dc3bac135e9f6243bd6d293e8c9293c73b9cd code was added
> to builtin/config.c to define a new function and a forward declaration
> for an array of unknown size. This causes a compile error under MSVC.
Hi Jeff
On 24.07.18 16:42, g...@jeffhostetler.com wrote:
> From: Jeff Hostetler
>
> Replace non-standard "\e" escape sequence with "\x1B".
This was already fixed in <20180708144342.11922-4-dev+...@drbeat.li>.
Cheers,
Beat
>
> In commit 7a17918c34f4e83982456ffe22d880c3cda5384f a trace
the parenthesising of i18n strings with
-DUSE_PARENS_AROUND_GETTEXT_N=no.
Signed-off-by: Beat Bolli
---
Now with -DUSE_PARENS_AROUND_GETTEXT_N=0 instead of =No.
This is the convenience knob for all developers that led to the series
bb/pedantic[1]. It does not depend on this series, though.
[1
On 23.07.18 20:53, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> In the interest of code hygiene, make it easier to compile Git with the
>> flag -pedantic.
>>
>> Pure pedantic compilation with GCC 7.3 results in one warning per use of
>> the translation
the parenthesising of i18n strings with
-DUSE_PARENS_AROUND_GETTEXT_N=no.
Signed-off-by: Beat Bolli
---
This is the convenience knob for all developers that led to the series
bb/pedantic[1]. It does not depend on this series, though.
[1] https://public-inbox.org/git/20180708144342.11922-1-dev
.
Signed-off-by: Beat Bolli
---
This is the convenience knob for all developers that led to the series
bb/pedantic[1]. It does not depend on this series, though.
[1] https://public-inbox.org/git/20180708144342.11922-1-dev+...@drbeat.li/T/#u
Makefile | 4
config.mak.dev | 4
2
The macro GIT_PATH_FUNC expands to a function definition that ends with
a closing brace. The extra semicolon produces a warning when compiling
with -pedantic.
Signed-off-by: Beat Bolli
---
Junio, this applies on top of pk/rebase-in-c.
Thanks, Beat
builtin/rebase.c | 4 ++--
1 file changed, 2
On 17.07.18 23:49, Beat Bolli wrote:
> On 06.07.18 14:08, Pratik Karki wrote:
>> +static GIT_PATH_FUNC(apply_dir, "rebase-apply");
>> +static GIT_PATH_FUNC(merge_dir, "rebase-merge");
>
> Maybe fix this up with
>
> -static GIT_PATH_FUNC(appl
On 06.07.18 14:08, Pratik Karki wrote:
> +static GIT_PATH_FUNC(apply_dir, "rebase-apply");
> +static GIT_PATH_FUNC(merge_dir, "rebase-merge");
Maybe fix this up with
-static GIT_PATH_FUNC(apply_dir, "rebase-apply");
-static GIT_PATH_FUNC(merge_dir, "rebase-merge");
+static
Hi Junio
Am 09.07.2018 23:45, schrieb Junio C Hamano:
Beat Bolli writes:
While developing 6aaded550 ("builtin/config: work around an unsized
array forward declaration", 2018-07-05), I have compiled Git with
CFLAGS="-std=c99 -pedantic".
Nicely done.
On 09.07.18 23:45, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> While developing 6aaded550 ("builtin/config: work around an unsized
>> array forward declaration", 2018-07-05), I have compiled Git with
>> CFLAGS="-std=c99 -pedantic".
&
On 09.07.18 23:34, Junio C Hamano wrote:
> Beat Bolli writes:
>
>> The marco GIT_PATH_FUNC expands to a complete statement including the
>> semicolon. Remove two extra trailing semicolons.
>
> Wait a bit. The observation in the log message and the
> implement
On 09.07.18 21:25, Beat Bolli wrote:
> While developing 6aaded550 ("builtin/config: work around an unsized
> array forward declaration", 2018-07-05), I have compiled Git with
> CFLAGS="-std=c99 -pedantic".
>
> This series fixes a few compiler warnings
Now that Unicode 11 has been announced[0], update the character
width tables to the new version.
[0] http://blog.unicode.org/2018/06/announcing-unicode-standard-version-110.html
Signed-off-by: Beat Bolli
---
unicode-width.h | 41 -
1 file changed, 28
On 09.07.18 20:46, Jeff King wrote:
> On Sun, Jul 08, 2018 at 04:43:38PM +0200, Beat Bolli wrote:
>
>> diff --git a/refs/refs-internal.h b/refs/refs-internal.h
>> index dd834314bd..a78b5cb803 100644
>> --- a/refs/refs-internal.h
>> +++ b/refs/refs-internal.h
ISO C forbids the conversion of void pointers to function pointers.
Introduce a context struct that encapsulates the function pointer.
Signed-off-by: Beat Bolli
---
string-list.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/string-list.c b/string
The macro GIT_PATH_FUNC expands to a function definition that ends with
a closing brace. Remove two extra semicolons.
While at it, fix the example in path.h.
Signed-off-by: Beat Bolli
---
path.h | 2 +-
sequencer.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
In ISO C, char constants must be in the range -128..127. Change the BOM
constants to char literals to avoid overflow.
Signed-off-by: Beat Bolli
---
utf8.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/utf8.c b/utf8.c
index d55e20c641..982217eec9 100644
--- a/utf8.c
Include iterator.h to define enum iterator_selection.
Signed-off-by: Beat Bolli
---
refs/refs-internal.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/refs/refs-internal.h b/refs/refs-internal.h
index dd834314bd..a78b5cb803 100644
--- a/refs/refs-internal.h
+++ b/refs/refs-internal.h
The "\e" escape is not defined in ISO C.
While on this line, add a missing space after the comma.
Signed-off-by: Beat Bolli
---
convert.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/convert.c b/convert.c
index 64d0d30e08..edebb946f5 100644
--- a/conve
Include protocol.h to define enum protocol_version.
Signed-off-by: Beat Bolli
---
connect.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/connect.h b/connect.h
index 0e69c6709c..c86f862f2f 100644
--- a/connect.h
+++ b/connect.h
@@ -1,6 +1,8 @@
#ifndef CONNECT_H
#define CONNECT_H
he trouble.
6) utf8.c: overflow of char values.
Used proper char literals for the BOM constants.
This series has patches for 2) to 6).
Regards,
Beat
[0]
https://public-inbox.org/git/53ab8626-f862-a732-b369-abeab69a4...@ramsayjones.plus.com/T/
Beat Bolli (6):
connect.h: avoid fo
On 09.07.18 18:33, Junio C Hamano wrote:
> Beat Bolli writes:
>
>>>> -static const char utf16_be_bom[] = {0xFE, 0xFF};
>>>> -static const char utf16_le_bom[] = {0xFF, 0xFE};
>>>> -static const char utf32_be_bom[] = {0x00, 0x00, 0xFE, 0xFF};
>>&g
Am 09.07.2018 16:48, schrieb Beat Bolli:
Hi Dscho
Am 09.07.2018 15:14, schrieb Johannes Schindelin:
Hi Beat,
On Sun, 8 Jul 2018, Beat Bolli wrote:
In ISO C, char constants must be in the range -128..127. Change the
BOM
constants to unsigned char to avoid overflow.
Signed-off-by: Beat
Hi Dscho
Am 09.07.2018 15:14, schrieb Johannes Schindelin:
Hi Beat,
On Sun, 8 Jul 2018, Beat Bolli wrote:
In ISO C, char constants must be in the range -128..127. Change the
BOM
constants to unsigned char to avoid overflow.
Signed-off-by: Beat Bolli
---
utf8.c | 10 +-
1 file
The "\e" escape is not defined in ISO C.
While on this line, add a missing space after the comma.
Signed-off-by: Beat Bolli
---
convert.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/convert.c b/convert.c
index 64d0d30e08..edebb946f5 100644
--- a/conve
ISO C forbids the conversion of void pointers to function pointers.
Introduce a context struct that encapsulates the function pointer.
Signed-off-by: Beat Bolli
---
string-list.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/string-list.c b/string
Include iterator.h to define enum iterator_selection.
Signed-off-by: Beat Bolli
---
refs/refs-internal.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/refs/refs-internal.h b/refs/refs-internal.h
index dd834314bd..a78b5cb803 100644
--- a/refs/refs-internal.h
+++ b/refs/refs-internal.h
In ISO C, char constants must be in the range -128..127. Change the BOM
constants to unsigned char to avoid overflow.
Signed-off-by: Beat Bolli
---
utf8.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/utf8.c b/utf8.c
index d55e20c641..833ce00617 100644
The marco GIT_PATH_FUNC expands to a complete statement including the
semicolon. Remove two extra trailing semicolons.
Signed-off-by: Beat Bolli
---
sequencer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sequencer.c b/sequencer.c
index 5354d4d51e..66e7073995 100644
Include protocol.h to define enum protocol_version.
Signed-off-by: Beat Bolli
---
connect.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/connect.h b/connect.h
index 0e69c6709c..c86f862f2f 100644
--- a/connect.h
+++ b/connect.h
@@ -1,6 +1,8 @@
#ifndef CONNECT_H
#define CONNECT_H
While developing 6aaded550 ("builtin/config: work around an unsized
array forward declaration", 2018-07-05), I have compiled Git with
CFLAGS="-std=c99 -pedantic".
This is an RFC patch series that fixes a few compiler warnings when
compiling with these options, always assuming that this is a
Hi Peff
On 05.07.18 21:38, Jeff King wrote:
> On Thu, Jul 05, 2018 at 08:34:45PM +0200, Beat Bolli wrote:
>
>> As reported here[0], Microsoft Visual Studio 2017.2 and "gcc -pedantic"
>> don't understand the forward declaration of an unsized static array.
>
th_options() is
called with the same arguments.
[0]: https://github.com/git-for-windows/git/issues/1735
[1]: https://groups.google.com/forum/#!topic/comp.lang.c.moderated/bmiF2xMz51U
Fixes https://github.com/git-for-windows/git/issues/1735
Reported-By: Karen Huang (via GitHub)
Signed-off-by:
On 25.04.18 02:32, Lev wrote:
> Hi list,
>
>
> I'm struggling with git connecting to Github.
>
> The problem might be SSL/TLS related.
>
> https://githubengineering.com/crypto-removal-notice/
>
> I suspect that my setup still uses tlsv1 or tlsv1.1.
>
> I've tried to explicitly set git to use
On Wed, Apr 25, 2018 at 09:05:56AM +0900, Junio C Hamano wrote:
> Johannes Sixt writes:
>
> > In modern setups, less, the pager, uses alternate screen to show
> > the content. When it is closed, it switches back to the original
> > screen, and all content is gone.
> >
> > It is
On Mon, Apr 23, 2018 at 11:13:41AM -0500, Jason B. Nance wrote:
> Hello all,
>
> We are seeing intermittent errors with Git 2.16.2.windows.1 on Windows
> 7 connecting to TFS 2017 (running in a Jenkins slave process):
>
> ERROR: Error cloning remote repo 'origin'
>
-for-windows/git/issues/1487 and subseqently in
https://public-inbox.org/git/f65780f29e48994380e2bce87c6f071101146...@deerlm99ex2msx.ww931.my-it-solutions.net/
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Cc: Alexander Gavrilov <angavri...@gmail.com>
Cc: Pat Th
In 89a70b80 ("t0302 & t3900: add forgotten quotes", 2018-01-03), quotes
were added to protect against spaces in $HOME. In the test_when_finished
handler, two files are deleted which must be quoted individually.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Diff to v
In 89a70b80 ("t0302 & t3900: add forgotten quotes", 2018-01-03), quotes
were added to protect against spaces in $HOME. In the test_when_finished
hander, two files are deleted which must be quoted individually.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
t/t390
Add the configuration option "jump.grepCmd" that allows to configure the
command that is used to search in grep mode. This allows the users of
git-jump to use ag(1) or ack(1) as search engines.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
contrib/git-jump/README | 3 +++
Add the configuration option "jump.grepCmd" that allows to configure the
command that is used to search in grep mode. This allows the users of
git-jump to use ag(1) or ack(1) as search engines.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
contrib/git-jump/README | 3 +++
--
„It takes love over gold” — Dire Straits
> On 7 Jul 2017, at 17:43, Junio C Hamano <gits...@pobox.com> wrote:
>
> Beat Bolli <dev+...@drbeat.li> writes:
>
>> Now that the Unicode 10 has been announced[0], update the character
>> width tables to th
Now that the Unicode 10 has been announced[0], update the character
width tables to the new version.
[0] http://blog.unicode.org/2017/06/announcing-unicode-standard-version-100.html
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.
Hi Dscho
On 2016-12-23 10:30, Johannes Schindelin wrote:
Hi Beat,
On Fri, 23 Dec 2016, Beat Bolli wrote:
On 22.12.16 18:08, Johannes Schindelin wrote:
> diff --git a/compat/winansi.c b/compat/winansi.c
> index cb725fb02f..590d61cb1b 100644
> --- a/compat/winansi.c
> +++ b/comp
On 22.12.16 18:08, Johannes Schindelin wrote:
> When determining whether a handle corresponds to a *real* Win32 Console
> (as opposed to, say, a character device such as /dev/null), we use the
> GetConsoleOutputBufferInfo() function as a tell-tale.
>
> However, that does not work for *input*
On 14.12.16 00:31, Beat Bolli wrote:
> [PATCH v2 4/6] update-unicode.sh: automatically download newer definition
> files
Dang! And again I'm not capable of putting an underline instead of the
dash...
Junio, would you please reword the subject to
Re: [PATCH v2 4/6] update_unic
The uniset upstream has accepted my patches that eliminate the Unicode
plane offsets from the output in '--32' mode.
Remove the corresponding filter in update_unicode.sh.
This also fixes the issue that the plane offsets were not removed from
the second uniset call.
Signed-off-by: Beat Bolli
The uniset upstream has added more commits that for example change the
hexadecimal output in '--32' mode to decimal. Let's pin the repo to a
commit that still outputs the width tables in the format we want.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
contrib/update-u
As it's used only by a tiny minority of the Git developer population,
this script does not belong into the main Git source directory.
Move it into contrib/ and adjust the paths to account for the new
location.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
.git
Checking just for the unicode data files' existence is not sufficient;
we should also download them if a newer version exists on the Unicode
consortium's servers. Option -N of wget does this nicely for us.
Reviewed-by: Torsten Bögershausen <tbo...@web.de>
Signed-off-by: Beat Boll
After the move into contrib/update-unicode, we no longer create the
unicode directory to have a clean working folder. Instead, the directory
of the script is used. This means that the subshell can be removed.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
contrib/update-u
This is v2 of my Unicode 9.0 series. After a short discussion [1], we
decided to move the generator script into contrib. This is what this
series now does first. The script is then updated in contrib.
Diff to v1:
- complete commit reordering
- fix nits in the commit messages
.gitignore
Rerunning update-unicode.sh that we fixed in the previous commits
produces these new tables.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.h | 131 +---
1 file changed, 107 insertions(+), 24 deletions(-)
diff
On 12.12.16 19:33, Junio C Hamano wrote:
> Torsten Bögershausen writes:
>
>> If I run ./update_unicode.sh on the latest master of
>> https://github.com/depp/uniset.git , commit
>> a5fac4a091857dd5429cc2d, I get a diff in unicode_width.h like
>> this:
>>
>> -{ 0x0300, 0x036F },
>>
On 12.12.16 19:12, Torsten Bögershausen wrote:
>
>>> Minor question, especially to the next commit:
>>> Should we make sure to checkout the exact version, which has been tested?
>>> In this case cb97792880625e24a9f581412d03659091a0e54f
>>>
>>> And this is for both a fresh clone and the git pull
On 2016-12-12 06:53, Torsten Bögershausen wrote:
On 2016-12-12 00:34, Beat Bolli wrote:
We need to track the new commits in uniset, otherwise their and our
code
get out of sync.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Junio, these go on top of my bb/unicode-9.0 branch,
We need to track the new commits in uniset, otherwise their and our code
get out of sync.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Junio, these go on top of my bb/unicode-9.0 branch, please.
Thanks!
update_unicode.sh | 5 +
1 file changed, 5 insertions(+)
diff
The uniset upstream has decided that decimal numbers are The True Way, so
let's convert them back to the usual format that's closer to the U+
standard.
The generated unicode_widths.h file again looks exactly the same as two
commits ago.
Signed-off-by: Beat Bolli <dev+...@drbeat
The uniset upstream has accepted my patches that eliminate the Unicode
plane offsets from the output in '--32' mode.
Remove the corresponding filter in update_unicode.sh.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
update_unicode.sh | 5 ++---
1 file changed, 2 insertions(+), 3 del
On 05.12.16 21:31, Junio C Hamano wrote:
> Torsten Bögershausen <tbo...@web.de> writes:
>
>> On Sat, Dec 03, 2016 at 10:00:47PM +0100, Beat Bolli wrote:
>>> Checking just for the unicode data files' existence is not sufficient;
>>> we should also dow
Rerunning update-unicode.sh that we fixed in the two previous commits
produces these new tables.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.h | 131 +---
1 file changed, 107 insertions(+), 24 deletions(-)
diff
Bögershausen <tbo...@web.de>
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
update_unicode.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index 3c84270..4c1ec8d 100755
--- a/update_unicode.sh
+++ b/update_unicode.sh
@@
Checking just for the unicode data files' existence is not sufficient;
we should also download them if a newer version exists on the Unicode
consortium's servers. Option -N of wget does this nicely for us.
Reviewed-by: Torsten Boegershausen <tbo...@web.de>
Signed-off-by: Beat Boll
On 03.12.16 17:40, Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= wrote:
> On Sat, Dec 03, 2016 at 02:19:31PM +0100, Beat Bolli wrote:
>> Checking just for the unicode data files' existence is not sufficient;
>> we should also download them if a newer version exists on the Unicode
Checking just for the unicode data files' existence is not sufficient;
we should also download them if a newer version exists on the Unicode
consortium's servers. Option -N of wget does this nicely for us.
Cc: Torsten Bögershausen <tbo...@web.de>
Signed-off-by: Beat Bolli <dev+...@
Bögershausen <tbo...@web.de>
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
update_unicode.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index 3c84270..4c1ec8d 100755
--- a/update_unicode.sh
+++ b/update_unicode.sh
@@ -30,7
Rerunning update-unicode.sh that we fixed in the two previous commits
produces these new tables.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.h | 131 +---
1 file changed, 107 insertions(+), 24 deletions(-)
diff
Checking just for the unicode data files' existence is not sufficient;
we should also download them if a newer version exists on the Unicode
consortium's servers. Option -N of wget does this nicely for us.
Cc: Torsten Bögershausen <tbo...@web.de>
Signed-off-by: Beat Bolli <dev+...@
.
Cc: Torsten Bögershausen <tbo...@web.de>
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Diff to v1:
- add Thorsten's Cc:
unicode_width.h | 17 -
update_unicode.sh | 2 +-
2 files changed, 1 insertion(+), 18 deletions(-)
diff --git a/unicode_width.h b/uni
the table.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.h | 17 -
update_unicode.sh | 2 +-
2 files changed, 1 insertion(+), 18 deletions(-)
diff --git a/unicode_width.h b/unicode_width.h
index 73b5fd6..02207be 100644
--- a/unicode_width.h
+++ b/unicode_w
A rerun of the previously fixed update-unicode.sh produces these new
tables.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
unicode_width.h | 122 +++-
1 file changed, 111 insertions(+), 11 deletions(-)
diff --git a/unicode_wid
Checking just for the files' existence is not enough; we should also
download them if a newer version exists on the Unicode servers.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
update_unicode.sh | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/update_unicod
On 26.08.16 21:16, Stefan Beller wrote:
> On Fri, Aug 26, 2016 at 11:24 AM, Junio C Hamano <gits...@pobox.com> wrote:
>> Beat Bolli <dev+...@drbeat.li> writes:
>>
>>> In 175d38c (SubmittingPatches: document how to reference previous commits,
>>>
In 175d38c (SubmittingPatches: document how to reference previous commits,
2016-07-28) the format for referring to older commits was specified.
Make the text generated by the "Copy commit summary" command match this
format.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
Cc: Pau
Amend the section on referencing previous commits with a hint to the
gitk command that was added exactly for this purpose.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
---
Documentation/SubmittingPatches | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documen
Ilya Tumaykin gmail.com> writes:
> $ git --no-pager log -1 --format='format:%+s%+b'
> Please fix.
Simply use `git --no-pager log -1 --format='format:%+s%n%+b'`
The message body excludes the empty line preceding it.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the
Junio C Hamano pobox.com> writes:
> + cd perf && $(MAKE) clean
I think the clean way to do this is
$(make) -C perf clean
Regards,
Beat
--
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
On 22.01.16 18:01, Johannes Schindelin wrote:
> The original patch was sent by Beat Bolli in
> http://thread.gmane.org/gmane.comp.version-control.git/281600
>
> My suggestion to extend it to respect gitattributes led to
> changes that broke the original patch.
>
> Since the
On 02.01.16 20:35, Junio C Hamano wrote:
> Ramsay Jones writes:
>
>> Hmm, I have never used a Mac, so I'm just guessing here, but
>> you could try something like (obviously untested!):
>>
>> diff --git a/t/t6023-merge-file.sh b/t/t6023-merge-file.sh
>> index
On 24.11.15 23:43, Beat Bolli wrote:
> On 24.11.15 09:21, Johannes Schindelin wrote:
>> Hi Beat,
>>
>> On Mon, 23 Nov 2015, Beat Bolli wrote:
>>
>>> When merging files in repos with core.eol = crlf, git merge-file inserts
>>> just a LF at the end of the
On 24.11.15 09:21, Johannes Schindelin wrote:
> Hi Beat,
>
> On Mon, 23 Nov 2015, Beat Bolli wrote:
>
>> When merging files in repos with core.eol = crlf, git merge-file inserts
>> just a LF at the end of the merge markers. Files with mixed line endings
>> ca
uot;binary
file matches".
Fixing this improves Git's behavior under Windows.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
Cc: Johannes Schindelin <johannes.schinde...@gmx.de>
---
builtin/merge-file.c | 1 +
ll-merge.c| 1 +
t/t6023-merge-file.sh | 7 +++
xdi
On 10.11.15 10:48, Peter Krefting wrote:
> Hi!
>
> After upgrading Git to 2.6.3 (from 2.5.0), gitk refuses to start when
> trying to load the Swedish translation if I pass it a commit range:
The patch can be found here:
http://article.gmane.org/gmane.comp.version-control.git/278863
Cheers,
s to unbreak our international
users.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
Cc: Paul Mackerras <pau...@samba.org>
---
gitk-git/gitk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gitk-git/gitk b/gitk-git/gitk
index 2028b55..fcc606e 100755
--- a/gitk-git/git
Git core has had automatic garbage collection for a long time.
Git-gui does not need a similar heuristic.
Signed-off-by: Beat Bolli <dev+...@drbeat.li>
Cc: Pat Thoyts <pattho...@users.sourceforge.net>
---
git-gui.sh | 3 ---
lib/database.tcl | 26 ---
Commit d835dbb9 ("gitk: Add a "Copy commit summary" command",
2015-08-13) in the upstream gitk repo added a new context menu entry.
Therefore, the line numbers of the entries below the new one need to be
adjusted when their text or state is changed.
Signed-off-by: Beat Boll
On 13.08.15 09:37, Paul Mackerras wrote:
On Sat, Jul 18, 2015 at 01:15:39PM +0200, Beat Bolli wrote:
When referring to earlier commits in commit messages or other text, one
of the established formats is
abbrev-sha (summary, author-date)
Add a Copy commit summary command to the context
1 - 100 of 115 matches
Mail list logo