Re: [PATCH V2 6/6] WIP/RFC/entry.c: fix a memleak

On Fri, Mar 27, 2015 at 08:14:28PM -0400, Eric Sunshine wrote: > On Friday, March 27, 2015, Eric Sunshine wrote: > > On Fri, Mar 27, 2015 at 6:32 PM, Stefan Beller wrote: > > > I observe that filter is going out of scope, but the > > > implementation proposed in this patch produces just a > > >

[PATCH 0/2] git-p4: Improve client path detection

I'm adding a test case for a scenario I was confronted with when using branch detection and a client view specification. It is possible that the implemented fix may not cover all possible scenarios, but there is no regression in the available tests. Vitor Antunes (2): git-p4: Check branch detect

[PATCH 1/2] git-p4: Check branch detection and client view together

Add failing scenario where using branch detection and a client view will break git p4 submit functionality. Signed-off-by: Vitor Antunes --- t/t9801-git-p4-branch.sh | 98 ++ 1 file changed, 98 insertions(+) diff --git a/t/t9801-git-p4-branch.sh b/t

[PATCH 2/2] git-p4: Improve client path detection when branches are used

A client view can be used to remap folder locations in the workspace. To support this when branch detection is enabled it is necessary to get the client path through "p4 where". This patch does two things to achieve this: 1. Force usage of "p4 where" when P4 branches exist in the git repository. 2

Re: Git Rev News edition 1 published

On Wed, Mar 25, 2015 at 11:00:21AM +0100, Christian Couder wrote: > Hi, > > Git Rev News edition 1 is now available: > > http://git.github.io/rev_news/edition-1.html > > Thanks a lot to all the contributors and helpers, especially Junio! > > Enjoy, > Christian and Thomas. Thank you for your wo

Re: how to make "full" copy of a repo

On Sat, Mar 28, 2015 at 03:56:37AM +0100, Christoph Anton Mitterer wrote: > Hey. > > I was looking for an ideally simple way to make a "full" copy of a git > repo. Many howtos are floating around on this on the web, with also lots > of voodoo. > > > First, it shouldn't be just a clone, i.o.w. >

Re: [PATCH V2 0/2] git-p4: Small updates to test cases

Will apply both. It seems that I am to blame for 1/2 for botching the shell syntax X-<. Thanks for fixing. I was not entirely happy with the "we could find either file10 or file11 because they are the same, so let's declare both are success" in the original, f69b3a93 (git p4 test: copy source in

Re: [PATCH 2/2] git-p4: Fix copy detection test

Vitor Antunes writes: > Vitor Antunes wrote: > >>Junio C Hamano wrote: >>>Pete, these tests blame to your 9b6513ac (git p4 test: split up big >>>t9800 test, 2012-06-27). I presume that you tested the result of >>>this splitting, but do you happen to know if we did something to >>>cause the tes

Arrow keys broken in gitk

Hi, in gitk on Debian jessie (Git version 2.1.4), the left/right arrow keys don't work in the text input fields. When I click into the SHA ID field or either search field and press the left or right arrow key, nothing happens. I'd expect the text cursor to move one character forward or back.

Re: [RFC/GSoC] Proposal Draft: Unifying git branch -l, git tag -l, and git for-each-ref

On 03/26/2015 10:07 PM, Jeff King wrote: On Mon, Mar 23, 2015 at 06:39:20PM +0530, karthik nayak wrote: > All three commands select a subset of the repository’s refs and print the > result. There has been an attempt to unify these commands by Jeff King[3]. I > plan on continuing his work[4] and

Re: how to make "full" copy of a repo

On 2015-03-28 03.56, Christoph Anton Mitterer wrote: > Hey. > > I was looking for an ideally simple way to make a "full" copy of a git > repo. Many howtos are floating around on this on the web, with also lots > of voodoo. > > > First, it shouldn't be just a clone, i.o.w. > - I want to have all

[PATCH] l10n: de.po: translate 99 new messages

Translate 99 messages came from git.pot update in c2ea120 (l10n: git.pot: v2.4.0 round 1 (99 new, 92 removed)). Signed-off-by: Ralf Thielow --- po/de.po | 289 ++- 1 file changed, 101 insertions(+), 188 deletions(-) diff --git a/po/de.

Re: [PATCH] l10n: de.po: translate 99 new messages

2015-03-28 20:38 GMT+01:00 Ralf Thielow : > > #: builtin/rm.c:17 > -#, fuzzy > msgid "git rm [] [--] ..." > -msgstr "git rm [Optionen] [--] [...]" > +msgstr "git rm [] [--] [...]" > The argument is not optional. Will be fixed in a reroll. -- To unsubscribe from this list: send the line "unsubsc

Re: how to make "full" copy of a repo

On Sat, Mar 28, 2015 at 7:52 PM, Torsten Bögershausen wrote: > On 2015-03-28 03.56, Christoph Anton Mitterer wrote: >> Hey. >> >> I was looking for an ideally simple way to make a "full" copy of a git >> repo. Many howtos are floating around on this on the web, with also lots >> of voodoo. >> >> >

git gui bug: filenames starting with ~

I didn't check if git claims to support arbitrary filenames. If a leading ~ isn't allowed, then this isn't a bug. I'm using git-gui version 0.19.GITGUI, from git version 2.3.4, from the Ubuntu PPA. git 2:2.3.4-1avh1~utopic1 steps to reproduce: mkdir -p git-shellmeta && cd git-shellmeta git

Re: [PATCH v2] config.c: split some variables to $GIT_DIR/config.worktree

On Fri, Mar 27, 2015 at 5:19 AM, Max Kirillov wrote: > On Thu, Mar 26, 2015 at 07:04:24PM +0700, Nguyễn Thái Ngọc Duy wrote: >> When you define $GIT_DIR/info/config.worktree, which contains of >> gitignore-style patterns (*), config variables that match these >> patterns will be saved in $GIT_DIR/

Re: how to make "full" copy of a repo

On Sat, 2015-03-28 at 15:31 +0100, Kevin D wrote: > What you are losing on clone is: > * config settings (this includes the configures remotes) > * hooks that would be okay... > * reflog (history of refs, though, by default disabled for bare > repositories) is there a way to get this copied?

Re: how to make "full" copy of a repo

On Sat, 2015-03-28 at 19:52 +0100, Torsten Bögershausen wrote: > As you only push to "new", "new" should have no information about > "old" or "temp". Exactly, that would be the goal. > > 1) Is it working like I assumed above? > > 2) Does that also copy things like git-config, hooks, etc.? > > 3