Re: Is cogito really this inefficient

2005-07-15 Thread Russell King
On Thu, Jul 14, 2005 at 05:29:09PM -0700, Linus Torvalds wrote: On Thu, 14 Jul 2005, Linus Torvalds wrote: I'll look into making diff-cache be more efficient. I normally don't use it myself, so I didn't bother (I use git-diff-files, which is way more efficient, but doesn't show the

[PATCH] Documentation: pull, push, packing repository and working with others.

2005-07-15 Thread Junio C Hamano
Describe where you can pull from with a bit more detail. Clarify description of pushing. Add a section on packing repositories. Add a section on recommended workflow for the project lead, subsystem maintainers and individual developers. Move Tag section around to make the flow of example

[PATCH] fetch/pull: support Cogito-style remote branch information.

2005-07-15 Thread Junio C Hamano
Since pull and fetch are done often against the same remote repository, keeping the URL to pull from along with the name of the head in $GIT_DIR/branches/$name like Cogito does makes a lot of sense. Adopt that and be compatible with Cogito for usability. Signed-off-by: Junio C Hamano [EMAIL

Re: [PATCH] fetch/pull: support Cogito-style remote branch information.

2005-07-15 Thread Linus Torvalds
Hmm.. This patch actually brings up two different issues - I actually prefer code and documentation to be separated. Finding the actual changes to code in this patch is made much harder by the fact that most of the changes are documentation updates. In many ways it would have been

Re: [PATCH] fetch/pull: support Cogito-style remote branch information.

2005-07-15 Thread Junio C Hamano
Linus Torvalds [EMAIL PROTECTED] writes: - I actually prefer code and documentation to be separated. ... first the actual change, then the docs updates. Understood. - I'd much rather have a generic address rewriting layer than a -b flag. I don't mind the shorthand at all, but

Re: git daemon

2005-07-15 Thread Linus Torvalds
On Fri, 15 Jul 2005, H. Peter Anvin wrote: Since it can be run as a sequestered user, and we now have plenty of CPU horsepower on the download servers, it seems like it should be an entirely sane thing to do. Goodie. Is this thing meant to be run from inetd, or is it a listen and fork

[PATCH] Documentation: adjust cvsimport command line.

2005-07-15 Thread Junio C Hamano
The cvsimport example in the cvs migration document was still using the old syntax for target repository after new and improved cvsimport-script was merged. Signed-off-by: Junio C Hamano [EMAIL PROTECTED] --- Documentation/cvs-migration.txt |2 +- 1 files changed, 1 insertions(+), 1

[PATCH] Documentation: update recommended workflow when working with others.

2005-07-15 Thread Junio C Hamano
Clarify that the hierarchy implied by the recommended workflow is only informal. Refer readers to nice illustration by Rundy Dunlap. Separate out the step to push to own public repository in the workflow. Signed-off-by: Junio C Hamano [EMAIL PROTECTED] --- Documentation/tutorial.txt | 65

Re: [PATCH] Documentation: update recommended workflow when working with others.

2005-07-15 Thread randy_dunlap
On Fri, 15 Jul 2005 20:56:12 -0700 Junio C Hamano wrote: Clarify that the hierarchy implied by the recommended workflow is only informal. Refer readers to nice illustration by Rundy Dunlap. Randy(please) Separate out the step to push to