[PATCH v2 4/6] git-remote-helpers.txt: rearrange description of capabilities

2012-11-27 Thread Max Horn
This also remove some duplication in the descriptions (e.g. refspec was explained twice with similar level of detail). Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 134 +++ 1 file changed, 56 insertions(+), 78 deletions(-) diff --git a

[PATCH v2 2/6] git-remote-helpers.txt: document missing capabilities

2012-11-27 Thread Max Horn
Specifically, document the 'export' and '(im|ex)port-marks' capabilities as well as the export command, which were undocumented (but in active use). Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 45 +--- 1 file changed,

[PATCH v2 1/6] git-remote-helpers.txt: document invocation before input format

2012-11-27 Thread Max Horn
Moreover, we now don't switch from discussing the input format to the invocation style and then back to input related stuff. Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 62 ++-- 1 file changed, 31 insertions(+), 31 deletions(-

Re: [PATCH 3/6] Fix grammar

2012-11-27 Thread Max Horn
On 27.11.2012, at 21:39, Junio C Hamano wrote: > Max Horn writes: > >> Subject: Re: [PATCH 3/6] Fix grammar > > Please run "git shortlog -200 --no-merges" from the tip of your > topic branch before sending a series out, and see if you can > immediately ident

[PATCH 5/6] Make clearer which commands must be supported for which capabilities

2012-11-27 Thread Max Horn
In particular, document 'list for-push' separately from 'list', as the former needs only be supported for the 'push' capability, and the latter only for fetch/import/export. In particular, a hypothetically 'push-only' helper only needs to support the for

[PATCH 1/6] Document invocation first, then input format

2012-11-27 Thread Max Horn
n't switch from discussing the input format to the invocation style and then back to input related stuff. Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 62 ++-- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/Documenta

[PATCH 3/6] Fix grammar

2012-11-27 Thread Max Horn
Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-remote-helpers.txt b/Documentation/git-remote-helpers.txt index db63541..7eb43d7 100644 --- a/Documentation/git-remote-helpers.txt +++ b

[PATCH 2/6] Document missing remote helper capabilities

2012-11-27 Thread Max Horn
The 'export' and '(im|ex)port-marks' capabilities were not documented at all Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 45 +--- 1 file changed, 42 insertions(+), 3 deletions(-) diff --git a/Documentation/git-r

[PATCH 4/6] Rearrange the description of remote helper capabilities

2012-11-27 Thread Max Horn
This also remove some duplication in the descriptions (e.g. refspec was explained twice with similar level of detail) Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 134 +++ 1 file changed, 56 insertions(+), 78 deletions(-) diff --git a

[PATCH 6/6] Remove 'for-push' from ref list attributes list, link to subsections

2012-11-27 Thread Max Horn
The documentation was misleading in that it gave the impression that 'for-push' could be used as a ref attribute in the output of the 'list' command. That is wrong. Signed-off-by: Max Horn --- Documentation/git-remote-helpers.txt | 13 - 1 file changed, 8 insert

[PATCH 0/6] Improve remote helper documentation

2012-11-27 Thread Max Horn
elt it was better to provide something than to do nothing and only complain, as I did previously on this subject ;-). Max Horn (6): Document invocation first, then input format Document missing remote helper capabilities Fix grammar Rearrange the description of remote helper capabilities

remote helper and relative local paths

2012-11-23 Thread Max Horn
I noticed a problem with remote helpers which is mainly about convenience, but still annoying enough that I wish it could be resolved; but I'd like some input on what the proper way would be... Here is the issue: cloning with relative paths is problematic (if not broken) when using remote-helpe

Re: [PATCH v5 15/15] fast-export: don't handle uninteresting refs

2012-11-22 Thread Max Horn
On 21.11.2012, at 06:08, Junio C Hamano wrote: > Jonathan Nieder writes: > >> Never mind that others have said that that's not the current interface >> (I don't yet see why it would be a good interface after a transition, >> but maybe it would be). Still, hopefully that clarifies the intended >

Re: gitpacker progress report and a question

2012-11-15 Thread Max Horn
On 15.11.2012, at 22:28, Eric S. Raymond wrote: > Some days ago I reported that I was attempting to write a tool that could > (a) take a git repo and unpack it into a tarball sequence plus a metadata log, > (b) reverse that operation, packing a tarball and log sequence into a repo. Ah, I could h

Re: [PATCH v5 11/15] remote-testgit: make clear the 'done' feature

2012-11-12 Thread Max Horn
On 11.11.2012, at 22:22, Felipe Contreras wrote: > On Sun, Nov 11, 2012 at 9:49 PM, Max Horn wrote: >> >> On 11.11.2012, at 14:59, Felipe Contreras wrote: >> >>> People seeking for reference would find it useful. >> >> Hm, I don't understand

Re: [PATCH v5 14/15] fast-export: make sure updated refs get updated

2012-11-11 Thread Max Horn
On 11.11.2012, at 14:59, Felipe Contreras wrote: > When an object has already been exported (and thus is in the marks) it's > flagged as SHOWN, so it will not be exported again, even if in a later > time it's exported through a different ref. > > We don't need the object to be exported again, bu

Re: [PATCH v5 02/15] remote-testgit: fix direction of marks

2012-11-11 Thread Max Horn
On 11.11.2012, at 14:59, Felipe Contreras wrote: > Basically this is what we want: > > == pull == > > testgit transport-helper > > * export -> import > > # testgit.marks git.marks > > == push == > > testgit transp

Re: [PATCH v5 05/15] Add new simplified git-remote-testgit

2012-11-11 Thread Max Horn
On 11.11.2012, at 14:59, Felipe Contreras wrote: > It's way simpler. It exerceises the same features of remote helpers. Typo: exerceises => exercises Cheers, Max -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordo

Re: [PATCH v5 11/15] remote-testgit: make clear the 'done' feature

2012-11-11 Thread Max Horn
On 11.11.2012, at 14:59, Felipe Contreras wrote: > People seeking for reference would find it useful. Hm, I don't understand this commit message. Probably means I am just too dumb, but since I am one of those people who would likely be seeking for reference, I would really appreciate if it cou

Re: Can git pull from a mercurial repository?

2012-09-26 Thread Max Horn
On 26.09.2012, at 09:38, Georgi Chorbadzhiyski wrote: > Around 09/25/2012 05:15 PM, Max Horn scribbled: >> I think there is a lot of demand for a "git-hg" bridge, a way to seemlessly >> access a Mercurial repository as if it was a git repository. A converse

Re: Can git pull from a mercurial repository?

2012-09-25 Thread Max Horn
Hi there, On 18.09.2012, at 14:40, Joachim Schmitz wrote: >> From: Andreas Ericsson [mailto:a...@op5.se] >> Sent: Tuesday, September 18, 2012 1:46 PM >> To: Joachim Schmitz >> Cc: git@vger.kernel.org >> Subject: Re: Can git pull from a mercurial repository? >> >> On 09/18/2012 01:22 PM, Joachim

Re: [PATCH] Change configure to check if pthreads are usable without any extra flags

2012-07-10 Thread Max Horn
On 10.07.2012, at 00:38, Junio C Hamano wrote: > Max Horn writes: > >> But all in all, I don't understand why this order independence >> seems to be so important? > > Not so important as long as it is made clear for later people to > patch that part of the c

Re: [PATCH] Change configure to check if pthreads are usable without any extra flags

2012-07-09 Thread Max Horn
On 09.07.2012, at 21:23, Junio C Hamano wrote: > Max Horn writes: > >>> would it be feasible for the purpose of >>> the check to tweak the definition of "works" used in the loop so that >>> it considers the warning as "not working"? >>

Re: [PATCH] Change configure to check if pthreads are usable without any extra flags

2012-07-09 Thread Max Horn
On 09.07.2012, at 19:44, Junio C Hamano wrote: > Max Horn writes: > >>>> diff --git a/configure.ac b/configure.ac >>>> index 4e9012f..d767ef3 100644 >>>> --- a/configure.ac >>>> +++ b/configure.ac >>>> @@ -1002,7 +1002,7 @@ if

Re: [PATCH] Change configure to check if pthreads are usable without any extra flags

2012-07-09 Thread Max Horn
On 09.07.2012, at 16:50, Junio C Hamano wrote: > Max Horn writes: > >> The configure script checks whether certain flags / libraries are >> required to use pthreads. But so far it did not consider the possibility >> that no extra compiler flags are needed (as is the ca

Re: [PATCH 2/2] Document rev^! and rev^@ as revision specifiers

2012-07-09 Thread Max Horn
> On 06.07.2012, at 21:18, Junio C Hamano wrote: > Max Horn writes: > >>>> +'{caret}!', e.g. 'HEAD{caret}!':: >>>> + A suffix '{caret}' followed by an exclamation mark >>>> + means commit '' but forces all

<    1   2