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 info
Junio C Hamano gits...@pobox.com:
Eric S. Raymond e...@thyrsus.com 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
Eric S. Raymond venit, vidit, dixit 22.11.2012 23:11:
Shawn Pearce spea...@spearce.org:
[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
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
Michael J Gruber g...@drmicha.warpmail.net:
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
Shawn Pearce spea...@spearce.org:
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
On Thu, Nov 22, 2012 at 11:11 PM, Eric S. Raymond e...@thyrsus.com wrote:
Shawn Pearce spea...@spearce.org:
[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
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
Shawn Pearce spea...@spearce.org:
[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
9 matches
Mail list logo
