Re: Requirements for integrating a new git subcommand

2012-11-26 Thread Peter Krefting
Eric S. Raymond: and (b) include the removal of import-directories.perl in my integration patch. Yes, please. -- \\// Peter - http://www.softwolves.pp.se/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo inf

Re: Requirements for integrating a new git subcommand

2012-11-25 Thread Eric S. Raymond
Junio C Hamano : > "Eric S. Raymond" writes: > > > While the weave operation can build a commit graph with any structure > > desired, an important restriction of the inverse (unraveling) > > operation is that it operates on *master branches only*. The unravel > > operation discards non-master-bra

Re: Requirements for integrating a new git subcommand

2012-11-25 Thread Junio C Hamano
"Eric S. Raymond" writes: > While the weave operation can build a commit graph with any structure > desired, an important restriction of the inverse (unraveling) > operation is that it operates on *master branches only*. The unravel > operation discards non-master-branch content, emitting a warni

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Christian Couder
On Thu, Nov 22, 2012 at 11:11 PM, Eric S. Raymond wrote: > Shawn Pearce : >> [Lots of helpful stuff ended by] >> > 4. How does "git help" work? That is, how is a subcommand expected >> > to know when it is being called to export its help text? >> >> IIRC "git help foo" runs "man git-foo". > > OK,

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Eric S. Raymond
Shawn Pearce : > Nope, it just has to be executable. We don't have any current Python > code. IIRC the last Python code was the implementation of > git-merge-recursive, which was ported to C many years ago. This turns out not to be quite true. The tree currently includes two Python scripts, a Pe

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Eric S. Raymond
Michael J Gruber : > Regarding git-weave, I'm wondering (without having looked at the code) > how this relates to git-archiv and git-fast-import/export, i.e. how much > this leverages existing infrastructure rather than reinventing the > wheel. Do your "trees" correspond to a "git tree"? The unrav

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Eric S. Raymond
Peter Krefting : > I was just about to say that the import direction of this seems to > fill the same need as contrib/fast-import/import-directories.perl > that I submitted a few years back. Yours was the closest in functionality, yes. > Your version seems only to be able to import a linear histo

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Peter Krefting
Eric S. Raymond: git-weave(1) Yes, there are scripts in contrib that do similar things. I was just about to say that the import direction of this seems to fill the same need as contrib/fast-import/import-directories.perl that I submitted a few years back. Your version seems only to be a

Re: Requirements for integrating a new git subcommand

2012-11-23 Thread Michael J Gruber
Eric S. Raymond venit, vidit, dixit 22.11.2012 23:11: > Shawn Pearce : >> [Lots of helpful stuff ended by] >>> 4. How does "git help" work? That is, how is a subcommand expected >>> to know when it is being called to export its help text? >> >> IIRC "git help foo" runs "man git-foo". > > OK, that

Re: Requirements for integrating a new git subcommand

2012-11-22 Thread Eric S. Raymond
Shawn Pearce : > [Lots of helpful stuff ended by] > > 4. How does "git help" work? That is, how is a subcommand expected > > to know when it is being called to export its help text? > > IIRC "git help foo" runs "man git-foo". OK, that makes sense. > > 5. I don't see any extensions written in Py

Re: Requirements for integrating a new git subcommand

2012-11-22 Thread Shawn Pearce
On Wed, Nov 21, 2012 at 9:30 PM, Eric S. Raymond wrote: > I have completed work on git-weave (the tool I had called 'gitpacker' in some > previous postings). I want to submit a patch that integrates it into git; > in hopes of smoothing the process I have some technical and procedural > questions.

Requirements for integrating a new git subcommand

2012-11-22 Thread Eric S. Raymond
I have completed work on git-weave (the tool I had called 'gitpacker' in some previous postings). I want to submit a patch that integrates it into git; in hopes of smoothing the process I have some technical and procedural questions. First, however, let me present the git-weave documentation f