[PATCH 2/2] bundle: Fix exclusion of annotated tags

2014-08-02 Thread Lukas Fleischer
In commit c9a42c4 (bundle: allow rev-list options to exclude annotated tags, 2009-01-02), support for excluding annotated tags outside the specified date range was added. However, the wrong order of parameters was chosen when calling memchr(). Fix this by swapping the character to search for with

[PATCH 1/2] t5704: Fix the test that checks for excluded tags

2014-08-02 Thread Lukas Fleischer
In c9a42c4 (bundle: allow rev-list options to exclude annotated tags, 2009-01-02), we added a test to check whether annotated tags, which fall outside the specified date range, are excluded from bundles. However, when initializing the repository, a command to create a lightweight tag was used. Fix

Re: [PATCH] git-svn: Avoid systematic prompt for client certificate when using git svn branch

2014-08-02 Thread Eric Wong
Thanks. In the future, it's expected to Cc: anybody who showed interest in previous versions of your patch. Monard Vong travelingsou...@gmail.com wrote: When a client certificate is required to connect to a Subversion repository, the certificate location and password may be stored in

With love

2014-08-02 Thread Birgit Rausing
I,Mrs Birgit authenticate this email, you can read about me on: http://en.wikipedia.org/wiki/Birgit_Rausing I have funds for you to manage and disburse to various charities of your choice. If you are sure you can handle this, it will be of help to you and others. Please reply if you are

Re: cherry picking and merge

2014-08-02 Thread Philip Oakley
From: Mike Stump mikest...@comcast.net Sent: Friday, August 01, 2014 11:10 PM On Aug 1, 2014, at 11:57 AM, Philip Oakley philipoak...@iee.org wrote: But that goes both ways, and is a philosophical issue about what is to be expected in various cases. The problem is, users expect merge to

Re: cherry picking and merge

2014-08-02 Thread Philip Oakley
From: Mike Stump mikest...@comcast.net Sent: Friday, August 01, 2014 11:24 PM On Aug 1, 2014, at 12:01 PM, Jakub Narębski jna...@gmail.com wrote: It can work in Subversion because Subversion stores information about what was merged in (and this includes cherry-picks, or whatever it is named in

Re: [PATCH] git-svn: Avoid systematic prompt for client certificate when using git svn branch

2014-08-02 Thread Monard Vong
Le 02/08/2014 12:07, Eric Wong a écrit : Thanks. In the future, it's expected to Cc: anybody who showed interest in previous versions of your patch. Monard Vong travelingsou...@gmail.com wrote: When a client certificate is required to connect to a Subversion repository, the certificate

With love

2014-08-02 Thread Birgit Rausing
I,Mrs Birgit authenticate this email, you can read about me on: http://en.wikipedia.org/wiki/Birgit_Rausing I have funds for you to manage and disburse to various charities of your choice. If you are sure you can handle this, it will be of help to you and others. Please reply if you are

Re: [PATCH v1 00/19] Enable options --signoff, --reset-author for pick, reword

2014-08-02 Thread Jeff King
On Tue, Jul 29, 2014 at 01:18:00AM +0200, Fabian Ruch wrote: this is a reroll of the patch series that enables rudimentary support of line options for git-rebase's to-do list commands and reimplements the well-known commands `reword` and `squash` in terms of a parameterised `do_pick`. I just

Re: Bug report about symlinks

2014-08-02 Thread René Scharfe
Am 01.08.2014 um 18:23 schrieb Junio C Hamano: René Scharfe l@web.de writes: # Create test repo with two directories with two files each. $ git init Initialized empty Git repository in /tmp/.git/ $ mkdir a b $ echo x a/equal $ echo x b/equal $ echo y a/different $ echo z b/different

[PATCH v2 0/1] doc: format-patch

2014-08-02 Thread Philip Oakley
Following the discussion at [1], I decided that while I felt the documentation changes were OK, the commit message need more explanation to cover the points raised in the discussion. Thus the only changes are to the commit message. In addition I'll separately cover the point raised about the DWIM

[PATCH v2 1/1] doc: format-patch: don't use origin as a branch name

2014-08-02 Thread Philip Oakley
Historically (5 Nov 2005 v0.99.9-46-g28ffb89) the git-format-patch used 'origin' as the upstream branch name. That name is now used as the nominal name for the upstream remote. While 'origin' would be DWIMmed (do what I mean) to be that remote's primary branch, do not assume the reader is ready

Re: cherry picking and merge

2014-08-02 Thread Philip Oakley
From: Mike Stump mikest...@comcast.net Sent: Friday, August 01, 2014 11:10 PM (part 2) On Aug 1, 2014, at 11:57 AM, Philip Oakley philipoak...@iee.org wrote: For some central control use styles, the ideas behind _distributed_ version control are anathema and (Git) just grinds away at the

Everday contents (was part of Re: What's cooking in git.git (Jul 2014, #04; Tue, 22))

2014-08-02 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Friday, July 25, 2014 11:08 PM ... | Individual Developer (Participant)[[Individual Developer (Participant)]] | ... | $ git pull

[PATCH 5/7] Documentation: git-init: reword parenthetical statements

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index bf0a7ae..96d6e67 100644 --- a/Documentation/git-init.txt +++

[PATCH 2/7] Documentation: git-init: list items facelift

2014-08-02 Thread Linus Arver
No textual change. Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 49 ++ 1 file changed, 28 insertions(+), 21 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index 5ed5859..45501d0

[PATCH] lots of documentation fixes/rewordings in git-init(1)

2014-08-02 Thread Linus Arver
Hello, I noticed a typo in git-init(1), which led me to some related changes. All changes are in Documentation/git-init.txt. I have cc'ed the people involved (thanks git-blame), just to make sure that my changes maintain technical accuracy. I've tested out the compiled man/html/etc. files and

[PATCH 1/7] Documentation: git-init: typographical fixes

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index afd721e..5ed5859 100644 --- a/Documentation/git-init.txt +++

[PATCH 6/7] Documentation: git-init: template directory: reword and cross-reference

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index 96d6e67..b94d165 100644 --- a/Documentation/git-init.txt +++

[PATCH 4/7] Documentation: git-init: --separate-git-dir: clarify

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index f21b85b..bf0a7ae 100644 --- a/Documentation/git-init.txt +++

[PATCH 3/7] Documentation: git-init: template directory: reword

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 14 +- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index 45501d0..f21b85b 100644 --- a/Documentation/git-init.txt +++

[PATCH 7/7] Documentation: git-init: flesh out example

2014-08-02 Thread Linus Arver
Signed-off-by: Linus Arver linusar...@gmail.com --- Documentation/git-init.txt | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt index b94d165..16e9f9c 100644 --- a/Documentation/git-init.txt +++

Re: [PATCH v3 1/3] lockfile.c: remove PATH_MAX limitation (except in resolve_symlink)

2014-08-02 Thread Torsten Bögershausen
On 08/01/2014 07:55 PM, Junio C Hamano wrote: Junio C Hamano gits...@pobox.com writes: Nguyễn Thái Ngọc Duy pclo...@gmail.com writes: Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com Somewhat underexplained, given that it seems to add some new semantics. +static void

A webes MAIL TEAM

2014-08-02 Thread Admin. webmail
A webes MAIL TEAM Figyelem! Ez a web-mail rendszergazda. Kérjük, tájékoztatni kell, hogy az e-mail szerver most lett frissítve, és az e-mail kell frissíteni immediately.This folyamat az, hogy a cég e-mail szerver frissítik, és a védett, mint mindig. Kérjük kattintson az alábbi linkre és

[PATCH] Documentation: avoid dangling modifier for imap-send

2014-08-02 Thread brian m. carlson
Avoid a nonsensical misreading by moving the modifier closer to the verb. Signed-off-by: brian m. carlson sand...@crustytoothpaste.net --- Documentation/git-imap-send.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-imap-send.txt

[PATCH v2] Documentation: avoid dangling modifier for imap-send

2014-08-02 Thread brian m. carlson
Avoid a nonsensical misreading by moving the modifier closer to the word it modifies. Signed-off-by: brian m. carlson sand...@crustytoothpaste.net --- Documentation/git-imap-send.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-imap-send.txt

Re: [PATCH] git-svn: doublecheck if really file or dir

2014-08-02 Thread Eric Wong
Andrej Manduch amand...@gmail.com wrote: On 07/24/2014 12:04 AM, Eric Wong wrote: Andrej Manduch amand...@gmail.com wrote: * this fixes 'git svn info `pwd`' buggy behaviour While your patch avoids an error, but the output isn't right, either. I tried it running in /home/ew/ruby, the

[PATCH] archive: honor tar.umask even for pax headers

2014-08-02 Thread brian m. carlson
git archive's tar format uses extended pax headers to encode metadata into the archive. Most tar implementations correctly treat these as metadata, but some that do not understand the pax format extract these as files instead. Apply the tar.umask setting to these entries to prevent tampering by