On Sun, 17 Apr 2005, Petr Baudis wrote:
> > Index: Makefile
> > ===================================================================
> > --- d662b707e11391f6cfe597fd4d0bf9c41d34d01a/Makefile (mode:100644
> > sha1:b2ce7c5b63fffca59653b980d98379909f893d44)
> > +++ 157b46ce1d82b3579e2e1258927b0d9bdbc033ab/Makefile (mode:100644
> > sha1:940ef8578cf469354002cd8feaec25d907015267)
> > @@ -35,6 +35,7 @@
> >
> > LIBS= -lssl -lz
> >
> > +http-pull: LIBS += -lcurl
> >
> > $(PROG):%: %.o $(COMMON)
> > $(CC) $(CFLAGS) -o $@ $^ $(LIBS)
>
> Whew. Looks like an awful trick, you say this works?! :-)
>
> At times, I wouldn't want to be a GNU make parser.
Yup. GNU make is big on the features which do the obvious thing, even when
you can't believe they work. This is probably why nobody's managed to
replace it.
> > Index: http-pull.c
> > ===================================================================
> > --- /dev/null (tree:d662b707e11391f6cfe597fd4d0bf9c41d34d01a)
> > +++ 157b46ce1d82b3579e2e1258927b0d9bdbc033ab/http-pull.c (mode:100644
> > sha1:106ca31239e6afe6784e7c592234406f5c149e44)
> > + url = malloc(strlen(base) + 50);
>
> Off-by-one. What about the trailing NUL?
I get length(base) + "object/"=8 + 40 SHA1 + 1 for '/' and 1 for NUL = 50.
> I think you should have at least two disjunct modes - either you are
> downloading everything related to the given commit, or you are
> downloading all commit records for commit predecessors.
>
> Even if you might not want all the intermediate trees, you definitively
> want the intermediate commits, to keep the history graph contignuous.
>
> So in git pull, I'd imagine to do
>
> http-pull -c $new_head
> http-pull -t $(tree-id $new_head)
>
> So, -c would fetch a given commit and all its predecessors until it hits
> what you already have on your side. -t would fetch a given tree with all
> files and subtrees and everything. http-pull shouldn't default on
> either, since they are mutually exclusive.
>
> What do you think?
I think I'd rather keep the current behavior and add a -c for getting the
history of commits, and maybe a -a for getting the history of commits and
their tress.
There's some trickiness for the history of commits thing for stopping at
the point where you have everything, but also behaving appropriately if
you try once, fail partway through, and then try again. It's on my queue
of things to think about.
-Daniel
*This .sig left intentionally blank*
-
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
