[PATCH] git-status-script was missed during the conversion from N -> A

2005-07-27 Thread Ryan Anderson
git-status-script was missed during the conversion from "N" to "A" as the new-file marker flag. Signed-off-by: Ryan Anderson <[EMAIL PROTECTED]> --- git-status-script |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) 10d81954c415dc46287f9d135e2b94302d4d7e84 diff --git a/git-status-scr

[PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread Ryan Anderson
Convert build process from recurse Make to a single Make The old Makefiles in Documentation/ and tools/ still exist until we feel confident that I didn't miss anything on this conversion. Most of this patch is fixing up the main Makefile to avoid overlapping target names. Signed-off-by: Ryan And

Git 1.0 Synopis (Draft v2)

2005-07-27 Thread Ryan Anderson
[This is still a draft, but I think I incorporated the suggestons from the last attempt.] Source Code Management with Git Git, sometimes called "global information tracker", is a "directory content manager". Git has been designed to handle absolutely massive projects with speed and efficiency, a

Re: Linux BKCVS kernel history git import..

2005-07-27 Thread David Woodhouse
On Tue, 2005-07-26 at 11:57 -0700, Linus Torvalds wrote: > If somebody adds some logic to "parse_commit()" to do the "fake parent" > thing, you can stitch the histories together and see the end result as one > big tree. Even without that, you can already do things like > > git diff v2.6.10

How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?

2005-07-27 Thread Josef Weidendorfer
Hi, if I clone a remote head other than master via Cogito with cg-clone host:path#remoteHead, work on this branch, and try to push back my changes with cg-push, I get the error "pushing to a different head not supported yet". As far as I can see, there is no support i

Re: [PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread A Large Angry SCM
Ryan Anderson wrote: Convert build process from recurse Make to a single Make Please explain the rational for this. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread Kirby C. Bohling
On Wed, Jul 27, 2005 at 10:25:10AM -0400, A Large Angry SCM wrote: > Ryan Anderson wrote: > >Convert build process from recurse Make to a single Make > > > > Please explain the rational for this. I'm new to the list, but given the subject, I'm fairly confident it's this. http://www.canb.auug.org

Re: [PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread A Large Angry SCM
Kirby C. Bohling wrote: On Wed, Jul 27, 2005 at 10:25:10AM -0400, A Large Angry SCM wrote: Ryan Anderson wrote: Convert build process from recurse Make to a single Make Please explain the rational for this. I'm new to the list, but given the subject, I'm fairly confident it's this. http://

Re: Linux BKCVS kernel history git import..

2005-07-27 Thread Linus Torvalds
On Wed, 27 Jul 2005, David Woodhouse wrote: > On Tue, 2005-07-26 at 11:57 -0700, Linus Torvalds wrote: > > If somebody adds some logic to "parse_commit()" to do the "fake parent" > > thing, you can stitch the histories together and see the end result as one > > big tree. Even without that, you c

Re: Linux BKCVS kernel history git import..

2005-07-27 Thread Linus Torvalds
On Wed, 27 Jul 2005, David Woodhouse wrote: > > Hm, OK. That works and can also be used for the "fake _absence_ of > parent" thing -- if I'm space-constrained and want only the history back > to some relatively recent point like 2.6.0, I can do that by turning the > 2.6.0 commit into an orphan i

Re: Linux BKCVS kernel history git import..

2005-07-27 Thread David Woodhouse
On Wed, 2005-07-27 at 08:29 -0700, Linus Torvalds wrote: > I used to think I wanted to, but these days I really don't. One of the > reasons is that I expect to try to pretty up the old bkcvs conversion some > time: use the name translation from the old "shortlog" scripts etc, and > see if I can do

Re: [PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread Junio C Hamano
Ryan Anderson <[EMAIL PROTECTED]> writes: > 003afd3ed1f83b4533b628182fa16c9ab0dc0467 > diff --git a/Documentation/Makefile.inc b/Documentation/Makefile.inc > new file mode 100644 > --- /dev/null > +++ b/Documentation/Makefile.inc > @@ -0,0 +1,50 @@ > +MAN1_TXT=$(wildcard Documentation/git-*.txt) >

Re: [PATCH] git-status-script was missed during the conversion from N -> A

2005-07-27 Thread Junio C Hamano
Ryan Anderson <[EMAIL PROTECTED]> writes: > git-status-script was missed during the conversion from "N" to "A" as > the new-file marker flag. Thanks. Applied and pushed out. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More major

Re: Stacked GIT 0.4

2005-07-27 Thread Catalin Marinas
On Tue, 2005-07-12 at 07:05 -0400, Bryan Larsen wrote: > Here's my wishlist. Hopefully I'll be able to dig in and help out. > > import: the complement to export A first implementation of 'import' is available in the tonight's snapshot (and in the StGIT git repository mirror). > template files f

Re: [PATCH/RFC] "Recursive Make considered harmful"

2005-07-27 Thread A Large Angry SCM
Junio C Hamano wrote: While I do not have strong objections to make the build process go faster, it is somewhat disturbing that the Makefile pieces maintained in subdirectories need to name things they touch using paths that include the subdirectory names. I do not have a better alternative to s

Re: Git 1.0 Synopis (Draft v2)

2005-07-27 Thread Junio C Hamano
Ryan Anderson <[EMAIL PROTECTED]> writes: > Source Code Management with Git Thanks for doing this. Generally looks excellent. > o Two, interchangeable, on-disk formats are used: > o An efficient, packed format that saves spaced and network > bandwidth. ??? "spaced" ??? > Or

Handover, Make

2005-07-27 Thread Brian O'Mahoney
First, congratulations Junio, on taking over this stuff, and all the best. Second, the killer argument, in the 'Recursive Make ... harmful' is the basic one that Recursive Makes breaks up the dependancy graph, and almost guarentees that it is wrong unless you do a lot of work to fix that artifact.

Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?

2005-07-27 Thread Junio C Hamano
Josef Weidendorfer <[EMAIL PROTECTED]> writes: > As far as I can see, there is no support in core GIT to make this ever work > (at least with get-send-packs), as "git-send-pack" only updates a set of > heads with the same name both locally and remote. Yes, it is my understanding that "clone" me