Hi Jakub,

On Thursday 03 May 2007 01:30, Jakub Narebski wrote:

quoted text
> >> What might help here is splitting repository into current (e.g. from
> >> OOo 2.0) and historical part,
> >
> > No, I don't want this ;-)
>
> I forgot to add there is possible to graft historical repository to the
> current work repository, resulting in full history available. For example
> Linux kernel repository has backported from BK historical repository, and
> there is grafts file which connect those two repositories.

Yes, grafting sounds really very promising! - I did not know about it.

quoted text
> >> and / or using shallow clone.
>
> git-clone(1):
>
> --depth <depth>::
>         Create a 'shallow' clone with a history truncated to the
>         specified number of revs.  A shallow repository has
>         number of limitations (you cannot clone or fetch from
>         it, nor push from nor into it), but is adequate if you
>         want to only look at near the tip of a large project
>         with a long history, and would want to send in a fixes
>         as patches.
>
> It is possible that those limitations will be lifted in the future
> (if possible), so there is alternate possibility to reduce needed
> disk space for git checkout. But certainly this is not for everybody.

It's probably too tight limitation for regular developers; for random hackers 
contributing a patch or two it could be a choice, right.

quoted text
> > We should better split the OOo sources; it's a process that already
> > started [UNO runtime environment vs. OOo without URE], and I proposed
> > some more changes already.
>
> In my opinion each submodule should be able to compile and test by
> itself. You can go X.Org route with splitting sources into modules...

Indeed, this is the case of URE - it is supposed to run by separately & be 
used even by other projects than OOo.

quoted text
> or you can make use of the new submodules support (currently plumbing
> level, i.e. low level commands), aka. gitlinks.

And this would be interesting for the translations, I guess...

quoted text
> The submodules support makes it possible to split sources into
> independent modules (parts), which can be developed independently,
> and which you can download (clone, fetch) or not, while making it
> possible to bind it all together into one superproject.
>
> See (somewhat not up to date) http://git.or.cz/gitwiki/SubprojectSupport
> page on git wiki.

... but will have a better look; thanks for the pointer!

quoted text
> Subversion doesn't have bisect, does it?

From what I know, it does not.

Thank you and others for all the input!

Last question: what is the status of the Win32 support?  I got a full clone 
using the Cygwin git 1.5.0 [it took 6hrs 20min on a Xen virtual machine; I 
have to try it with real hardware], MinGW version did not work for me too 
well :-(  Are there any other options?  Is 
http://git.or.cz/gitwiki/WindowsInstall up-to-date?

Regards,
Jan
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html