Antw: Re: Enhancement Request: "locale" git option

>>> Ralf Thielow schrieb am 06.12.2014 um 20:28 in Nachricht : > 2014-12-05 16:45 GMT+01:00 Torsten Bögershausen : >> >> I do not know who was first, and who came later, but >> > chverfolgen> >> >> uses "versioniert

[PATCH] t: support clang/gcc AddressSanitizer

When git is compiled with "-fsanitize=address" (using clang or gcc >= 4.8), all invocations of git will check for buffer overflows. This is similar to running with valgrind, except that it is more thorough (because of the compiler support, function-local buffers can be checked, too) and runs much f

Antw: Re: Enhancement Request: "locale" git option

>>> Ralf Thielow schrieb am 04.12.2014 um 20:02 in Nachricht : > Hi Ulrich, > > 2014-12-04 8:32 GMT+01:00 Ulrich Windl : >> Hi! >> >> I'm native German, but German git messages confuse me (yopu'll have to > correlate them with the man pages). At the moment git uses the > > What in particular ma

Re: [PATCH] fsck: properly bound "invalid tag name" error message

On Mon, Dec 08, 2014 at 12:48:12AM -0500, Jeff King wrote: > Note that when fscking tags with "index-pack --strict", this > is even worse. index-pack does not add a trailing > NUL-terminator after the object, so we may actually read > past the buffer and print uninitialized memory. Running > t5302

[PATCH] fsck: properly bound "invalid tag name" error message

When we detect an invalid tag-name header in a tag object, like, "tag foo bar\n", we feed the pointer starting at "foo bar" to a printf "%s" formatter. This shows the name, as we want, but then it keeps printing the rest of the tag buffer, rather than stopping at the end of the line. Our tests did

Re: [PATCH] Show number of commits being rebased interactively

Hi, > These lines above "---" will become the only log message text, which > is probably not what you intended. Use "-- >8 --" marker instead > (that is a perforation line with a pair of scissors on it)? Thanks, hopefully fixed below. >> +commitcount=$(git stripspace --strip-comments <"$todo" |

RE: git push hung?

No cc's please, I am on the list. > -Original Message- > From: Torsten Bögershausen > Sent: Sunday, December 07, 2014 12:58 > > On 2014-12-07 15.24, Jason Pyeron wrote: > > I am trying to push to our local intranet git (smart https > behind apache), and it has been at this point for 10+

Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly

Philip Oakley писал в своём письме Sun, 07 Dec 2014 20:48:05 +0300: From: "Роман Донченко" Jeff King писал в своём письме Sun, 07 Dec 2014 12:18:59 +0300: On Sat, Dec 06, 2014 at 10:36:23PM +0300, Роман Донченко wrote: One final note on this bit of code: if there are multiple encoded

Re: git push hung?

On 2014-12-07 15.24, Jason Pyeron wrote: > I am trying to push to our local intranet git (smart https behind apache), > and it has been at this point for 10+ hours. > > jpyeron@black /projects/git/git > $ GIT_TRACE=1 git push > 09:08:45.662902 git.c:349 trace: built-in: git 'push' >

Re: How to repair a shallow clone (?)

On 2014-12-07 12.44, Duy Nguyen wrote: >> Is this a known issue/problem ? > > No. > Thanks everybody for the support. The machine was equipped with git version 1.7.10.4 in /usr/bin. I installed 2.1 or so under /usr/local/bin, (and even /root/bin) thinking that this would help, but it didn't.

Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly

From: "Роман Донченко" Jeff King писал в своём письме Sun, 07 Dec 2014 12:18:59 +0300: On Sat, Dec 06, 2014 at 10:36:23PM +0300, Роман Донченко wrote: The RFC says that they are to be concatenated after decoding (i.e. the intervening whitespace is ignored). Thanks. Both patches look go

Re: Cannot reset a repo

arghh, sorry that's embarrassing. I was sure that the Mac filesystem was case sensitive by default, because it's unix based... Thanks for your support. > Am 07.12.2014 um 11:06 schrieb Torsten Bögershausen : > > On 06.12.14 14:39, Martin Wendt wrote: >>> Am 06.12.2014 um 13:14 schrieb Torsten B

Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly

Jeff King писал в своём письме Sun, 07 Dec 2014 12:18:59 +0300: On Sat, Dec 06, 2014 at 10:36:23PM +0300, Роман Донченко wrote: The RFC says that they are to be concatenated after decoding (i.e. the intervening whitespace is ignored). Thanks. Both patches look good to me, and I'd be happy

git push hung?

I am trying to push to our local intranet git (smart https behind apache), and it has been at this point for 10+ hours. jpyeron@black /projects/git/git $ GIT_TRACE=1 git push 09:08:45.662902 git.c:349 trace: built-in: git 'push' 09:08:45.662902 run-command.c:341 trace: run_com

Re: How to repair a shallow clone (?)

On Sat, Dec 6, 2014 at 7:23 PM, Torsten Bögershausen wrote: > I share a bare repo with Sparkleshare which does an auto-synch. > Now the synch had stopped, and trying to push to the central repo > by hand gives this: > > > > git push origin master > fatal: protocol error: expected old/new/ref, got

Re: How to repair a shallow clone (?)

From: "Trần Ngọc Quân" On 06/12/2014 19:23, Torsten Bögershausen wrote: I think I started to clone the repo in a shallow way (SparkleShare asked if I want to clone the complete history, and I probably answered "no" ) Is there a way to repair this situation ? (Except doing a complete re-clone ?

[PATCH] git-svn: Support for git-svn propset

This change allows git-svn to support setting subversion properties. Very useful for manually setting properties when committing to a subversion repo that *requires* properties to be set without requiring moving your changeset to separate subversion checkout in order to set props. This change is

[PATCH] git-svn: propset support v3

Added: Eric Sunshine's: - suggestion to include the comment about propset only working on files with content changes. Eric Wong's: - use && to chain commands throughout tests - use svn_cmd wrapper throughout tests - show $! in die messages - favor $(...) over `...` in tests - make new_props an

Re: Fetching a specific commit by commit ID

On 06 Dec 2014, at 16:52, brian m. carlson wrote: >> - more interestingly: is there any reason why git fetch should not >> support fetching by commit id? There are real world use cases where >> this can be very useful, for instance when references on the remote >> have been overwritten or dele

Re: [PATCH/RFC] doc: document error handling functions and conventions (Re: [PATCH 03/14] copy_fd: pass error message back through a strbuf)

On Fri, Dec 05, 2014 at 10:00:05AM -0800, Junio C Hamano wrote: > Jeff King writes: > > > The only downside I can think of is that we may truncate the message in > > exceptional circumstances. But is it really any less helpful to say: > > > > error: unable to open file: some-incredibly-long-fi

Re: Accept-language test fails on Mac OS

On 07.12.14 08:18, Jeff King wrote: > On Sat, Dec 06, 2014 at 10:04:06PM +0100, Torsten Bögershausen wrote: > >> I get this: >> >> >> expecting success: >> check_language "ko-KR, *;q=0.1" ko_KR.UTF-8 de_DE.UTF-8 ja_JP.UTF-8 >> en_US.UTF-8 && >> check_language "de-DE, *;q=0.1" ""

Re: [PATCH] git-svn: Support for git-svn propset

On 12/6/14, 9:42 PM, Eric Wong wrote: Alfred Perlstein wrote: This change allows git-svn to support setting subversion properties. Very useful for manually setting properties when committing to a subversion repo that *requires* properties to be set without requiring moving your changeset to s

Re: Accept-language test fails on Mac OS

On 07.12.14 07:54, Yi, EungJun wrote: > I'm sorry for bothering you, but could you tell me the result of > "locale" command without "-a" option? What I want to know is locale > environment variables and its values, so I want to reproduce the test > failures on my laptop. > (Just for completeness:)

Re: [PATCH] git-svn: propset support v2

On Sat, Dec 6, 2014 at 5:29 PM, Alfred Perlstein wrote: > I have incorporated Eric Wong's feedback into the git-svn propset support > patch. > > There is a nit that I want to point out. The code does not support adding > props > unless there are also content changes to the files as well. You c

Re: [PATCH] git-svn: Support for git-svn propset

On Sun, Dec 7, 2014 at 3:00 AM, Torsten Bögershausen wrote: > On 2014-12-07 06.45, Torsten Bögershausen wrote: > [] >>> + >>> +test_expect_success 'add multiple props' ' >>> +git svn propset svn:keywords "FreeBSD=%H" foo && >>> +git svn propset fbsd:nokeywords yes foo && >>> +echo hell

Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly

On Sat, Dec 06, 2014 at 10:36:23PM +0300, Роман Донченко wrote: > The RFC says that they are to be concatenated after decoding (i.e. the > intervening whitespace is ignored). Thanks. Both patches look good to me, and I'd be happy to have them applied as-is. I wrote a few comments below, but in al

Re: [PATCH/RFC v2] Squashed changes for multiple worktrees vs. submodules

On Sun, Dec 07, 2014 at 08:42:30AM +0200, Max Kirillov wrote: >> *) I'd love to see a solution for sharing the object database >>between otherwise unrelated clones of the same project (so >>that fetching in one clone updates the objects in the common >>dir and gc cannot throw anything a

Re: [PATCH] git-svn: Support for git-svn propset

On 2014-12-07 06.45, Torsten Bögershausen wrote: [] >> + >> +test_expect_success 'add multiple props' ' >> +git svn propset svn:keywords "FreeBSD=%H" foo && >> +git svn propset fbsd:nokeywords yes foo && >> +echo hello >> foo && >> +git commit -m "testing propset" foo && >> +git