From: Beat Bolli
When referencing earlier commits in new commit messages or other text,
one of the established formats is
commit ("", )
Add a "Copy commit summary" command to the context menu that puts this
text for the currently selected commit on the clipboard. This makes it
easy for our
From: Beat Bolli
Now that the whole file is generated by one single command, the command
group is no longer needed.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.s
From: Beat Bolli
By using a here document instead of the echo/uniset sequence, the final
structure of the generated file becomes obvious.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/update_unicode.sh b/upd
From: Beat Bolli
The value is the same on both uniset invocations, so "Don't Repeat
Yourself" applies.
Since we're in a subshell already, there's no need to unset UNICODE_DIR
at the end.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
From: Beat Bolli
Instead of capturing the output of each echo and uniset invocation, wrap
the whole section in a group command and redirect its output all at
once.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --gi
From: Beat Bolli
"uniset/uniset" is a relative path; there's no need to prefix it with "./".
Signed-off-by: Beat Bolli
---
update_unicode.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index bed8916..f5cc14b 100755
--- a/update_
From: Beat Bolli
By using a here document instead of the echo/uniset sequence, the final
structure of the generated file becomes obvious.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/update_unicode.sh b/upd
From: Beat Bolli
The value is the same on both uniset invocations, so "Don't Repeat
Yourself" applies.
Since we're in a subshell already, there's no need to unset UNICODE_DIR
at the end.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
From: Beat Bolli
"uniset/uniset" is a relative path; there's no need to prefix it with "./".
Signed-off-by: Beat Bolli
---
update_unicode.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index bed8916..f5cc14b 100755
--- a/update_
From: Beat Bolli
Now that the whole file is generated by one single command, the command
group is no longer needed.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.s
From: Beat Bolli
Instead of capturing the output of each echo and uniset invocation, wrap
the whole section in a group command and redirect its output all at
once.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --gi
From: Beat Bolli
By using printf instead of the echo/uniset sequence, the final structure
of the generated file becomes obvious.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/update_unicode.sh b/update_un
From: Beat Bolli
Now that the whole file is generated by one single command, the command
group is no longer needed.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index 6196
From: Beat Bolli
The value is the same on both uniset invocations, so "Don't Repeat
Yourself" applies.
Since we're in a subshell already, there's no need to unset UNICODE_DIR
at the end.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
From: Beat Bolli
"uniset/uniset" is a relative path; there's no need to prefix it with "./".
Signed-off-by: Beat Bolli
---
update_unicode.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index bed8916..f5cc14b 100755
--- a/update_
From: Beat Bolli
Instead of capturing the output of each echo and uniset invocation, wrap
the whole section in a group command and redirect its output all at
once.
Signed-off-by: Beat Bolli
---
update_unicode.sh | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --gi
On September 6, 2014 at 4:53 PM "René Scharfe" wrote:
> Am 06.09.2014 um 21:26 schrieb dev:
> >
> >
> >
> > Solaris 10 with Oracle Studio 12.3 compiler tools. A lengthy
> > maillist
> > discussion last week sorted out the previous release o
Build on Solaris 10 of latest git tarball fails thus :
CC tag.o
CC trace.o
"trace.c", line 219: error: identifier redeclared: trace_strbuf
current : function(pointer to const char, pointer to const
struct strbuf {unsigned long alloc, unsigned long len, pointer to char
buf}) retu
On August 28, 2014 at 11:26 AM Matthieu Moy
wrote:
> dev writes:
>
> > Actually I found a file called GIT-BUILD-OPTIONS :
>
> That's a generated file (not included by the Makefile, but by some
> shell
> scripts later), don't edit it. Use config.mak for your bu
On August 28, 2014 at 8:05 PM "brian m. carlson"
wrote:
> On Thu, Aug 28, 2014 at 12:54:30AM -0400, dev wrote:
> > Funny I don't see libcurl anywhere. Thought that was needed? Also
> > the
> > RUNPATH
> > and RPATH look duplicated and slightly bo
On August 28, 2014 at 10:50 AM Jeff King wrote:
> On Thu, Aug 28, 2014 at 10:16:48AM -0400, dev wrote:
>
> > # gmake CFLAGS="$CFLAGS" LDFLAGS="$LD_OPTIONS" NEEDS_LIBICONV=Yes \
> > > SHELL_PATH=/usr/local/bin/bash \
> > > SANE_TOOL_PATH=/usr/loc
reached
Writing perl.mak for Git
Writing MYMETA.yml and MYMETA.json
/bin/sh: gtar: /bin/shnot found
: gtar: not found
gmake[1]: *** [install] Error 1
gmake: *** [install] Error 2
Well that is maddening.
Is there some magic somewhere to use ordinary POSIX tar ?
Also, what is shnot ?
dev
--
To u
On August 27, 2014 at 6:28 PM Jonathan Nieder
wrote:
> Hi again,
>
> dev wrote:
>
> > So I guess I have to create a config.mak file from somewhere.
>
> Sorry, let's take a step back.
Actually I think we have some real progress to report here. After
scann
On August 27, 2014 at 6:28 PM Jonathan Nieder
wrote:
> Hi again,
>
> dev wrote:
>
> > So I guess I have to create a config.mak file from somewhere.
>
> Sorry, let's take a step back.
>
> What exact commands do you use to build, starting from a pristine
>
On August 27, 2014 at 4:06 PM Jeff King wrote:
> On Wed, Aug 27, 2014 at 03:48:40PM -0400, dev wrote:
>
> > $ gzip -dc $SRC/git-2.0.4.tar.gz | tar -xf -
> > $ mv git-2.0.4 git-2.0.4_SunOS5.10_sparcv9.002
> > $
> > $ cd git-2.0.4_SunOS5.10_sparcv9.002
> > $
Good day gentlemen. With coffee in hand I am taking a crack and getting
git to compile out of the sources neatly and therefore I have hit a
few bumps. Inline comments below :
On August 27, 2014 at 3:28 PM Jeff King wrote:
> On Wed, Aug 27, 2014 at 03:15:05PM -0400, dev wrote:
>
> >
e linkage to libintl
should look in /usr/local/lib if the LD_LIBRARY_PATH and other env vars
are setup correctly. However the Makefile's seem to miss this fact and
-lintl needs to be manually hacked into place.
Still doesn't "just build" yet. Getting there :-\
dev
--
To unsubs
27 matches
Mail list logo
