Re: Interested in helping open source friends on HP-UX?

On Wed, Feb 18, 2015 at 05:00:07PM +0100, H.Merijn Brand wrote: > On Wed, 10 Dec 2014 23:46:25 -0800, Junio C Hamano > wrote: > > > Hello, all. > > > > H. Merijn Brand runs a few HP-UX boxes to help perl5 and other open > > source communities, wants help porting more recent Git on these > > boxe

Re: Undelivered Mail Returned to Sender

On Feb 20, 2015, at 9:16 PM, Technext wrote: > Thanks Junio for the prompt reply! :) Yes, that's exactly how i would like > things to be. I'll definitely try to push this thing and see if this flow > can be implemented. > > However, can you please guide me whether there's any way i could have >

[PATCH] sha1_name: use strlcpy() to copy strings

Use strlcpy() instead of calling strncpy() and then setting the last byte of the target buffer to NUL explicitly. This shortens and simplifies the code a bit. Signed-of-by: Rene Scharfe --- sha1_name.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/sha1_name.c b/sha

[PATCH] pretty: use starts_with() to check for a prefix

Simplify the code and avoid duplication by using starts_with() instead of strlen() and strncmp() to check if a line starts with "encoding ". Signed-off-by: Rene Scharfe --- pretty.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pretty.c b/pretty.c index 9d34d02..7b49304 100

[PATCH] for-each-ref: use skip_prefix() to avoid duplicate string comparison

Use skip_prefix() to get the part after "color:" (if present) and only compare it with "reset" instead of comparing the whole string again. This gets rid of the duplicate "color:" part of the string constant. Signed-off-by: Rene Scharfe --- builtin/for-each-ref.c | 7 +++ 1 file changed, 3 i

[PATCH] connect: use strcmp() for string comparison

Get rid of magic string length constants and simply compare the strings using strcmp(). This makes the intent of the code a bit clearer. Signed-off-by: Rene Scharfe --- connect.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/connect.c b/connect.c index 062e133..2a5c400 1

question about resume support.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi... Im wonder there is planned or maybe there is support of resuming interrupted git operation e.g. cloning repositories? Not sure about how hard that could be to implement, but greatly should decrease of bandwidth used by persons with weak network

Re

Sind Sie dabei, eine geschäftliche oder persönliche Darlehen in Höhe von bis zu $ 200.000.000,00 interessiert   Erschwinglich: Unternehmenskredite ab Zinssatz 3,0% und unverbindlich.   Behoben: gelten für 10 Minuten, die Finanzierung innerhalb von 2 Wochen.   Name.   Menge benötigt.   Kreditla

[REQUEST] another --cleanup mode for commit

Hey. Right now, all --cleanup modes for commit (except verbatim) seem to remove all "unnecessary" whitespace and collapse consecutive empty lines. I use already vim to show me any such things and when I don't remove it then, this usually means I want to have it intentionally (especially consecuti

[cosmetic bug?] needlessly(?) executable files

Hey. Just a question about files like: .git/config .git/hooks/*.sample Is there any reason that these are created executable? Especially the config file? I know the hooks are already disabled by being named .sample, but having them executable just increases the chance that one accidentally fires

[BUG] git mangles up commit messages on rebase

Hey. When I do a simple interactive rebase, e.g. something like this: edit 78f3ba8 editing or just rewriting this commit pick b621076 foo pick e06c28e this one had a "verbatim" commit message pick c0a447f bar and one of the commit messages from the children I edit/rewrite had a commit message tha

[PATCH v2 1/3] connect.c: allow ssh://user@[2001:db8::1]/repo.git

The ssh:// syntax was added in 2386d65822c91, it accepted ssh://user@2001:db8::1/repo.git, which is now legacy. Over the years the parser was improved to support [] and port numbers, but the combination of ssh://user@[2001:db8::1]:222/repo.git did never work. The only only way to use a user name,

[PATCH v2 3/3] t5500: show user name and host in diag-url

The URL for ssh may have include a username before the hostname, like ssh://user@host/repo. When literal IPV6 addresses are used together with a username, the substring "user@[::1]" must be converted into "user@::1". Make that conversion visible for the user, and write userandhost in the diagnosti

[PATCH v2 2/3] t5601: add more test cases for IPV6

Test the parsing of literall IPV6 addresses more systematically: - with and without brackets (e.g. ::1 [::1]) - with brackets and port number: (e.g. [::1]:22) - with username (e.g. user@::1) - with username and brackets: Because user@[::1] was not supported on older Git version, [user@::1] had

Re: git blame swallows up lines in case of mixed line endings

On 2015-02-19 14.48, Sokolov, Konstantin (ext) wrote: > Hi Folks, > > I encounter unexpected behavior in the following case: > > file content: > > line1 > line2 > line3 > line4 > > This is what I get as console output (on Windows): > >> git blame -s file.txt > 7db36436 1) line1 > line3436 2) l