Re: [PATCH 00/13] remote-hg: general updates

On Thu, Apr 4, 2013 at 12:42 AM, Felipe Contreras wrote: > On Wed, Apr 3, 2013 at 6:25 PM, Max Horn wrote: >> On 03.04.2013, at 03:31, Felipe Contreras wrote: > >>> I only learned about it recently, I've looked at the history and to me >>> it seems rather chaotic, and a lot of the code was simply

Re: [PATCH] update pasky's email address

Eric Wong writes: > Mail to pa...@suse.cz is bouncing. > > Signed-off-by: Eric Wong > --- > I noticed this when I attempted to reply to Thomas's email: > > http://mid.gmane.org/f3d238a4c6cfbc6d68f2c4fa285aefa93acf4b7d.1365027616.git.tr...@inf.ethz.ch > > .mailmap

Re: [PATCH 00/13] remote-hg: general updates

On Wed, Apr 3, 2013 at 6:25 PM, Max Horn wrote: > On 03.04.2013, at 03:31, Felipe Contreras wrote: >> I only learned about it recently, I've looked at the history and to me >> it seems rather chaotic, and a lot of the code was simply copied from >> git-remote-hg without comment. > > gitifyhg was

Re: Two potential bugs in aliases that expand to shell commands

On Wed, Apr 03, 2013 at 07:05:33PM -0700, Han wrote: > There appears to be another case string values need to be enclosed in > quotes, which is a shell command where you want to preserve quote > characters (not leading or trailing); a minimal example is > > shortcut = !cd "" && pwd Yes. You mu

Re: Composing git repositories

Junio C Hamano writes: > Jonathan Nieder writes: > >> If you are curious, at a quieter time it might be useful to ask for >> pointers to the discussions that led to the current design, and folks >> on the list might be glad to help. > > Not on the current design but the discussion before that ro

Two potential bugs in aliases that expand to shell commands

These might just be documentation bugs. Aliases that expand to shell commands are only documented fairly superficially, but `git help config` does say: "If the alias expansion is prefixed with an exclamation point, it will be treated as a shell command." It also says, nearer the beginning: "Strin

[PATCH] update pasky's email address

Mail to pa...@suse.cz is bouncing. Signed-off-by: Eric Wong --- I noticed this when I attempted to reply to Thomas's email: http://mid.gmane.org/f3d238a4c6cfbc6d68f2c4fa285aefa93acf4b7d.1365027616.git.tr...@inf.ethz.ch .mailmap| 1 + Documentation/

Re: [PATCH] git-svn: avoid self-referencing mergeinfo

Michael Contreras wrote: > When svn.pushmergeinfo is set, the target branch is included in the > mergeinfo if it was previously merged into one of the source branches. > SVN does not do this. > > Remove merge target branch path from resulting mergeinfo when > svn.pushmergeinfo is set to better ma

Recently banned from #git

Hello, I am somewhat new to git and I was asking a lot of questions in #git without properly checking the manuals or knowing enough about linux. I want to apologize for my behavior and explain that I will do everything on my part to help answer the question on my own and read the documentation. I

Re: [PATCH] perl: redirect stderr to /dev/null instead of closing

Thomas Rast wrote: > Closing stderr is a bad idea anyway: there is a very real chance that > we print fatal error messages to some other file that just happens to > be opened on the now-free FD 2. So let's not do that. 100% agreed. FD 0, 1, and 2 should not be closed, way too much potential for

You do not have permission to post to the ms...@lists.myitforum.com list

Sorry, you do not have permission to post to the ms...@lists.myitforum.com mailing list. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 00/13] remote-hg: general updates

On 03.04.2013, at 03:31, Felipe Contreras wrote: > On Tue, Apr 2, 2013 at 4:23 PM, Max Horn wrote: >> >> On 02.04.2013, at 22:09, John Keeping wrote: >> >>> On Tue, Apr 02, 2013 at 01:02:49PM -0600, Felipe Contreras wrote: Here is the next round of patches for remote-hg, some which have b

Re: [PATCH] git-web--browse: recognize iTerm as a GUI terminal on OS X

On Wed, Mar 27, 2013 at 10:43 AM, Junio C Hamano wrote: [snip] > If that approach is better than what you originally sent, then yes. > > But I do not use OS X, so you may need to pay attention to possible > complaints and comments from other Mac users on this list for a > while---there may be peop

Re: cd

On 04/03/2013 04:49 PM, jpinheiro wrote: Hi all, We are students from Universidade do Minho in Portugal, and we are using git in project as a case study. While experimenting with git we found an unexpected behavior with git rm. Here is a trace of the unexpected behavior: $ git init $ mkdir D $

[PATCH] perl: redirect stderr to /dev/null instead of closing

On my system, t9100.1 triggers the following warning: ==352== Syscall param write(buf) points to uninitialised byte(s) ==352==at 0x57119C0: __write_nocancel (in /lib64/libc-2.17.so) ==352==by 0x56AC1D2: _IO_file_write@@GLIBC_2.2.5 (in /lib64/libc-2.17.so) ==352==by 0x56AC0B1: n

Re: [PATCH] Documentation/git-commit: reword the --amend explanation

Sent: Wednesday, April 03, 2013 9:04 PM Junio C Hamano writes: Yes, and since then we gained --no-edit option and such, so "editor starts off" also needs to be rethought, no? The original wording with "seeded" may have a better chance of survival, I suspect, but still needs some adjustment.

Re: [PATCH V3 2/5] Help.c use OPT_BOOL and refactor logic

Sent: Wednesday, April 03, 2013 2:13 AM Junio C Hamano writes: You are creating a gap in the output so that you can add some more stuff in later patches, which is fine, but I do not think we call that kind of change a "refactor" ;-). The change looks fine. I'll queue what I suggested on 'pu

Re: Github Data Challenge

Please disregard this email, I made a mistake. * Valentin Haenel [2013-04-03]: > Hi, > > hat jemand Lust da mit zu machen: > > https://github.com/blog/1450-the-github-data-challenge-ii > > ? > > V- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to m

Re: [PATCH] Documentation: Strip texinfo anchors to avoid duplicates

On 03.04.2013 22:07, Junio C Hamano wrote: > I see why duplicates are bad, but does that mean not having any is > better? I'd say yes: duplicate anchors cause current versions of texinfo to reject the document outright, and older versions will likely cause a broken interpretation of any anchor nam

Re: Behavior of git rm

On Wed, Apr 03, 2013 at 10:35:52AM -0700, Junio C Hamano wrote: > > diff --git a/builtin/rm.c b/builtin/rm.c > > index dabfcf6..7b91d52 100644 > > --- a/builtin/rm.c > > +++ b/builtin/rm.c > > @@ -110,7 +110,7 @@ static int check_local_mod(unsigned char *head, int > > index_only) > >

Github Data Challenge

Hi, hat jemand Lust da mit zu machen: https://github.com/blog/1450-the-github-data-challenge-ii ? V- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: RFC: allowing multiple parallel sequencers

On Tue, Apr 02, 2013 at 03:06:51PM -0400, Neil Horman wrote: > On Tue, Apr 02, 2013 at 11:06:28AM -0700, Junio C Hamano wrote: > > Neil Horman writes: > > > > > I've recently started looking into the possibility of having git support > > > multiple in-progress sequencers, and wanted to solicit

Re: [PATCH] Documentation: Strip texinfo anchors to avoid duplicates

Martin von Gagern writes: > This keeps texinfo 5.x happy. See https://bugs.gentoo.org/464210. I see why duplicates are bad, but does that mean not having any is better? > > Signed-off-by: Martin von Gagern > --- > Documentation/cat-texi.perl | 1 + > 1 file changed, 1 insertion(+) > > diff --

Re: [PATCH] Documentation/git-commit: reword the --amend explanation

Junio C Hamano writes: > Yes, and since then we gained --no-edit option and such, so "editor > starts off" also needs to be rethought, no? The original wording > with "seeded" may have a better chance of survival, I suspect, but > still needs some adjustment. So here is my attempt. We still ne

[PATCH/RFC 1/3] Teach mv to move submodules together with their work trees

Currently the attempt to use "git mv" on a submodule errors out with: fatal: source directory is empty, source=, destination= The reason is that mv searches for the submodule with a trailing slash in the index, which it doesn't find (because it is stored without a trailing slash). As it doesn't f

[PATCH/RFC 3/3] Teach mv to update the path entry in .gitmodules for moved submodules

Currently using "git mv" on a submodule moves the submodule's work tree in that of the superproject. But the submodule's path setting in .gitmodules is left untouched, which is now inconsistent with the work tree and makes git commands that rely on the proper path -> name mapping (like status and d

[PATCH/RFC 2/3] Teach mv to move submodules using a gitfile

When moving a submodule which uses a gitfile to point to the git directory stored in .git/modules/ of the superproject two changes must be made to make the submodule work: the .git file and the core.worktree setting must be adjusted to point from work tree to git directory and back. Achieve that b

[PATCH/RFC 0/3] Teach mv to move submodules

This is the last topic I intend to finish before preparing the recursive submodule update. The other prerequisites for that next step are Heiko's "allow more sources for config values" and "fetch moved submodules on-demand" topics, which are necessary to populate submodules that were not present in

[PATCH] Documentation: Strip texinfo anchors to avoid duplicates

This keeps texinfo 5.x happy. See https://bugs.gentoo.org/464210. Signed-off-by: Martin von Gagern --- Documentation/cat-texi.perl | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/cat-texi.perl b/Documentation/cat-texi.perl index dbc133c..b52660d 100755 --- a/Documentation/cat-t

[PATCH v2] diffcore-break: don't divide by zero

When the source file is empty, the calculation of the merge score results in a division by zero. In the situation: == preimage == == postimage == F (empty file) F (a large file) E (a new empty file) it does not make sense to cons

Re: [PATCH 2/2] bisect: avoid signed integer overflow

Signed-off-by: John Keeping --- Changes since v1: - Change the function signature instead of casting a value in the function. - This lets us remove an existing cast. bisect.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bisect.c b/bisect.c index bd1b7b5..374d9e2 100

Re: [PATCH] git-tag(1): we tag HEAD by default

Thomas Rast writes: > Yann Droneaud writes: > ... >> Is there any other kind of object that can be tagged ... and what is >> the purpose of this ? > > Any object type, including tags. Signed tags of other tags probably > make sense if you want to express extra approval on top of the original >

Re: [PATCH] git-tag(1): we tag HEAD by default

Thomas Rast writes: > There are some instances with the comma style: > > $ git grep ',.*::$' Documentation/*.txt > Documentation/blame-options.txt:-L ,, -L ::: > Documentation/config.txt:gitcvs.dbuser, gitcvs.dbpass:: > Documentation/config.txt:http.lowSpeedLimit, http.lowSpeedTime:: >

Re: [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients

Jeff King writes: > On Wed, Apr 03, 2013 at 12:10:38PM -0400, Jeff King wrote: > >> Hmm. This is testing just the ref advertisement. It would be nice to see >> a complete transaction tested with namespaces turned on. Something like >> this (squashed into your patch) seems to work for me: > > Actu

Re: [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients

John Koleszar writes: > diff --git a/t/t5561-http-backend.sh b/t/t5561-http-backend.sh > index b5d7fbc..97f97a1 100755 > --- a/t/t5561-http-backend.sh > +++ b/t/t5561-http-backend.sh > @@ -23,6 +23,10 @@ GET() { > test_cmp exp act > } > > +GET_BODY() { > + curl "$HTTPD_URL/$SMART/rep

Re: Behavior of git rm

Jeff King writes: > Of the two situations, I think the first one is less likely to be > destructive (noticing that a file is already gone via ENOTDIR), as we > are only proceeding with the index deletion, and we end up not touching > the filesystem at all. Nice to see sound reasoning. > > diff

Re: [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients

On Wed, Apr 03, 2013 at 12:10:38PM -0400, Jeff King wrote: > Hmm. This is testing just the ref advertisement. It would be nice to see > a complete transaction tested with namespaces turned on. Something like > this (squashed into your patch) seems to work for me: Actually, I guess the point of yo

Re: git https transport and wrong password

On Wed, Apr 03, 2013 at 10:12:12AM -0400, Jeff King wrote: > I would expect without the username in the URL for it to make only two > requests: one to get the first 401, then git collects the credentials, > then a follow-up with the credentials. But instead we get: > > $ GIT_CURL_VERBOSE=1 git l

Re: [PATCH] http-backend: respect GIT_NAMESPACE with dumb clients

On Wed, Apr 03, 2013 at 08:52:09AM -0700, John Koleszar wrote: > + SMART=smart > + git ls-remote public >expected && > + grep /$NS/ expected >/dev/null && > + GET_BODY "info/refs" >actual && > + test_cmp expected actual && > + GET_BODY "info/refs?service=git-upload-pack"

Re: Behavior of git rm

On Wed, Apr 03, 2013 at 07:50:24AM -0700, jpinheiro wrote: > While experimenting with git we found an unexpected behavior with git rm. > Here is a trace of the unexpected behavior: > > $ git init > $ mkdir D > $ echo "Hi" > D/F > $ git add D/F > $ rm -r D > $ echo "Hey" > D > $ git rm D/F > warni

[PATCH] http-backend: respect GIT_NAMESPACE with dumb clients

Filter the list of refs returned via the dumb HTTP protocol according to the active namespace, consistent with other clients of the upload-pack service. Signed-off-by: John Koleszar --- This should incorporate all of Junio's and Josh's comments. Also fixes a bug in the first patch where the HEAD

Re: [PATCH] git-tag(1): we tag HEAD by default

Yann Droneaud writes: > Hi, > > Le 03.04.2013 16:27, Thomas Rast a écrit : >> +, :: >> +The object that the new tag will refer to, usually a commit. >> +Defaults to HEAD. > > Is there any other kind of object that can be tagged ... and what is > the purpose of this ? Any object type, in

Re: [PATCH] git-tag(1): we tag HEAD by default

Hi, Le 03.04.2013 16:27, Thomas Rast a écrit : The | argument is actually not explained anywhere (except implicitly in the description of an unannotated tag). Write a little explanation, in particular to cover the default. +, :: + The object that the new tag will refer to, usually a

Re: [PATCH] git-tag(1): we tag HEAD by default

Thomas Rast writes: > Junio C Hamano writes: > >> Thomas Rast writes: >> >>> +, :: >>> + The object that the new tag will refer to, usually a commit. >>> + Defaults to HEAD. >> >> Shouldn't this be more like this: >> >> :: >> :: >> Your explanation here... > > Hmm, you're right

Build system bugs related to handling of 'LIBS' environment variable

Hello, Git fails to build if LIBS contains -lpthread. To reproduce: export LIBS=-lpthread ./configure make V=1 git-credential-store The bug is that linker command line does not contain -lpthread, so linking fails. configure respects LIBS and finds that it does not have to add anything fo

Re: [PATCH] git-tag(1): we tag HEAD by default

Junio C Hamano writes: > Thomas Rast writes: > >> +, :: >> +The object that the new tag will refer to, usually a commit. >> +Defaults to HEAD. > > Shouldn't this be more like this: > > :: > :: > Your explanation here... Hmm, you're right, but we seem to be fairly inconsist

[ANNOUNCE] Sharness v0.3.0

Hi, I've released a new version of Sharness [1] -- the test harness library derived from Git's test lib [2]. This release is all about bringing upstream fixes and improvements from Git to Sharness [3]. Now Sharness only lacks a few of the generic functions provided by Git's test lib, e.g. test_de

Re: [PATCH] git-tag(1): we tag HEAD by default

Thomas Rast writes: > The | argument is actually not explained anywhere > (except implicitly in the description of an unannotated tag). Write a > little explanation, in particular to cover the default. > > Signed-off-by: Thomas Rast > --- > > Prompted by a question on IRC about the default valu

Re: [PATCH] Documentation/git-commit: reword the --amend explanation

Carlos Martín Nieto writes: > The explanation for 'git commit --amend' talks about preparing a tree > object, which shouldn't be how user-facing documentation talks about > commit. > > Reword it to say it works as usual, but replaces the current commit. > --- Sign-off? > The current text is fro

Re: [PATCH 1/3] remote-helpers: fix the run of all tests

Jeff King writes: > On Tue, Apr 02, 2013 at 06:53:28PM +0200, Torsten Bögershausen wrote: > >> > I think the check for duplicate-numbers is the only one that does not >> > make sense. >> [] >> Not sure about that, I send a suggestion of a patch in a minute. >> Highlights: >> 1) - rename the cont

Behavior of git rm

Hi all, We are students from Universidade do Minho in Portugal, and we are using git in project as a case study. While experimenting with git we found an unexpected behavior with git rm. Here is a trace of the unexpected behavior: $ git init $ mkdir D $ echo "Hi" > D/F $ git add D/F $ rm -r D $ e

cd

Hi all, We are students from Universidade do Minho in Portugal, and we are using git in project as a case study. While experimenting with git we found an unexpected behavior with git rm. Here is a trace of the unexpected behavior: $ git init $ mkdir D $ echo "Hi" > D/F $ git add D/F $ rm -r D $ e

Re: [PATCH v2] count-objects: output "KiB" instead of "kilobytes"

Mihai Capotă writes: > The code uses division by 1024. The master branch count-objects manual also > uses "KiB". > > Also updated the code that reads count-objects output (t5301, t5700, t7408, > and > git-cvsimport) and the Git User's Manual. > > Signed-off-by: Mihai Capotă > --- > Documentati

Re: [PATCH] test-lint-duplicates: Only check for numbered test cases

On Wed, Apr 03, 2013 at 07:54:02AM +0200, Torsten Bögershausen wrote: > Running make inside contrib/remote-helpers fails in "test-lint-duplicates" > > This was because the regexp checking for duplicate numbers strips everything > after the first "-" in the filename, including the prefix. > > As

[PATCH] git-tag(1): we tag HEAD by default

The | argument is actually not explained anywhere (except implicitly in the description of an unannotated tag). Write a little explanation, in particular to cover the default. Signed-off-by: Thomas Rast --- Prompted by a question on IRC about the default value. Do we actually read our own docs

Re: git https transport and wrong password

[+cc Daniel for curl questions below] On Wed, Apr 03, 2013 at 12:43:02PM +0300, Mikko Rapeli wrote: > Maybe my git installation was incomplete before when running from ~/bin since > I was not able to set break points to http_request() and some debug code > was not there until I ran git through bi

[PATCH] Documentation/git-commit: reword the --amend explanation

The explanation for 'git commit --amend' talks about preparing a tree object, which shouldn't be how user-facing documentation talks about commit. Reword it to say it works as usual, but replaces the current commit. --- The current text is from 2006, which I guess explains the wording. Document

[PATCH v2] count-objects: output "KiB" instead of "kilobytes"

The code uses division by 1024. The master branch count-objects manual also uses "KiB". Also updated the code that reads count-objects output (t5301, t5700, t7408, and git-cvsimport) and the Git User's Manual. Signed-off-by: Mihai Capotă --- Documentation/user-manual.txt |4 ++-- builtin/c

Re: check-attr doesn't respect recursive definitions

Thanks for the clarifications. Just a quick comment about the summary: Jeff King wrote: > Yeah, I had the same thought. So you would have to either: > > 1. Hook the feature into git-archive, which knows about how it > recurses, and can report the correct set of paths. > > or > > 2. Tell

Re: git https transport and wrong password

Maybe my git installation was incomplete before when running from ~/bin since I was not able to set break points to http_request() and some debug code was not there until I ran git through bin-wrappers in the source tree. I added some debug prints to http.c functions http_request() and handle_curl

[PATCH] cherry-pick: better error message when the parameter is a non-commit

When copy&paste goes wrong, and the user e.g. tries to cherry-pick a blob, the error message used to be: fatal: BUG: expected exactly one commit from walk Instead, now it is: fatal: Can't cherry-pick a blob Signed-off-by: Miklos Vajna --- sequencer.c | 9 - 1 file chan

Re: [PATCH 00/13] remote-hg: general updates

>> * internally, the marks are using the hg sha1s instead of the hg rev ids. >> The latter are not necessarily invariant, and using the sha1s makes it much >> easier to recover from semi-broken states. > > I doubt this makes any difference (except for more wasted space). I think this is definite

Re: [PATCH 00/13] remote-hg: general updates

On Tue, Apr 2, 2013 at 7:31 PM, Felipe Contreras wrote: >> * added many new test cases, sadly still including some xfails. Several of >> these (both passing and xfailing) also apply to remote-hg (i.e. the issue is >> also present in contrib's remote-hg) > > I ran these test-cases with remote-hg

Re: ZSH segmentation fault while completing "git mv dir/"

Manlio Perillo writes: > By the way: have you filled a bug report to Debian? No, but this is a bug touching very few users, in Debian stable which is reaching its end of life. I do not think the Debian folks would be interested in fixing this non-security, non-critical bug now. -- Matthieu Moy

You'll also find complex Pandora sale who are a popular topic

You might seeking out [url=http://www.cheappandorabuyshop.co.uk/] pandora uk[/url] for Connecticut, most definitely all the truly trendy style anklet bracelets. They can be a completely unique and additionally basic version of precious jewelry which usually arose in Denmark. There is other desi

I merely ended up being generally in close proximity to a lot of don't known tiffany uk variety

Most of the food morning ended up being generally fantastic. Most of the spouses shifted by way of, [url=http://www.buytiffanyringsshop.co.uk/] tiffany uk[/url] the majority of by way of shimmering is appropriate for. Surely your current sister-in-law, as opposed to using whom I ran across a nu

pandora bracelet charms guaranteed the standard of the majority of the valuable jewellery for top level form

What is much better within [url=http://www.pndoracharmonlineshop.ca/] pandora charms[/url] is usually which often as the trinket would have been a large number of masterpieces, all of the provider additionally offers a number of items you could make use of. Computer mindset for that recipient,

thomas sabo uk carry an exceptional verity about designs and additionally ways

The new magnifying glaas thomas sabo uk carry an exceptional verity about designs and additionally ways equally, all the texture and consistency along with the phenomena experience smaller bubble magnifying glaas golf balls throughout the working surfac