* Norbert Thiebaud nthieb...@gmail.com schrieb:
big_snip /
Just wondering: do you want to bisect the whole bundle of trees
at once or just single packages ?
cu
--
--
Enrico Weigelt, metux IT service -- http://www.metux.de/
On Sun, Feb 06, 2011 at 05:44:03AM -0600, Norbert Thiebaud
nthieb...@gmail.com wrote:
humm... what build.git ? :-) on master I do not even clone build.git
anymore...
Then bootstrap.git, you get it. :)
Con: it seriously increase the barrier of entry. git already scare
some people... git +
On Mon, Feb 7, 2011 at 9:02 AM, Miklos Vajna vmik...@frugalware.org wrote:
On Sun, Feb 06, 2011 at 05:44:03AM -0600, Norbert Thiebaud
nthieb...@gmail.com wrote:
humm... what build.git ? :-) on master I do not even clone build.git
anymore...
Then bootstrap.git, you get it. :)
;-)
(I
On Sun, 2011-02-06 at 05:44 -0600, Norbert Thiebaud wrote:
Note that the main drawback of our current approach is indeed the
bisection problem. It would be certainly be convinient to be able to
bisect on the entire set of repos... but how much pain/risk do we want
to take to improve that
On Mon, Feb 07, 2011 at 04:29:23PM +, Michael Meeks
michael.me...@novell.com wrote:
Could we do some sort of date based bisection ? or does that not work
because the patches are not in chronological order really ;-)
It's possible to do g checkout @{2011-02-07}, but then we have to
On Mon, Feb 07, 2011 at 09:38:14AM -0600, Norbert Thiebaud
nthieb...@gmail.com wrote:
How about having a after-push git-hook in the master branch in our
git.fdi/git/libreoffice/* git repos that generate the list of
HEAD-sha1
that was you should be able to almost-completely bisect.
sure in
On Mon, Feb 7, 2011 at 10:29 AM, Michael Meeks michael.me...@novell.com wrote:
On Sun, 2011-02-06 at 05:44 -0600, Norbert Thiebaud wrote:
Note that the main drawback of our current approach is indeed the
bisection problem. It would be certainly be convinient to be able to
bisect on the entire
On Mon, Feb 7, 2011 at 11:10 AM, Miklos Vajna vmik...@frugalware.org wrote:
On Mon, Feb 07, 2011 at 09:38:14AM -0600, Norbert Thiebaud
nthieb...@gmail.com wrote:
How about having a after-push git-hook in the master branch in our
git.fdi/git/libreoffice/* git repos that generate the list of
On Mon, Feb 07, 2011 at 12:18:39PM -0600, Norbert Thiebaud
nthieb...@gmail.com wrote:
The problem of the tinderbox approach is the coarse granularity (it is
not uncommon to have 1/2 a dozen or more of independent commit between
2 build, the reliability (tinderbox sometime are down and this is
On Mon, Feb 07, 2011 at 10:33:00PM +0100, Miklos Vajna vmik...@frugalware.org
wrote:
Automatic git commit --amend is really dangerous, I would not do it.
It's not an accident non-fastforwards are rejected while pushing.
It turns out I misunderstood it, I thought this is about git commit
On Mon, Jan 31, 2011 at 03:39:41PM +0100, Jan Holesovsky ke...@suse.cz wrote:
Can you please do a bit of research in that regard, and summarize how we
would gain from using git submobule?
To my understanding, in short:
git submodules are not like how svn externals are usually used. svn
* Norbert Thiebaud nthieb...@gmail.com schrieb:
Note that the main drawback of our current approach is indeed the
bisection problem. It would be certainly be convinient to be able to
bisect on the entire set of repos... but how much pain/risk do we want
to take to improve that aspect of
I meant the repos in the bootstrap repo, of course, not the build repo.
Am 31.01.2011 16:23, schrieb Norbert Thiebaud:
I concur. my limited understanding of how submodule works lead me to
believe that
it would not be a nice fit with what we do
1/ it is more appropriate when the 'modules' have
Hi Tobias,
On 2011-01-30 at 20:56 +0100, Tobias Rosenberger wrote:
is there a reason why you don't use git submodule for managing the
other repos in the build repo?
The reason is that so far nobody researched that enough, to be able to
judge if it would help us, or not :-) From what I know
On Mon, Jan 31, 2011 at 8:39 AM, Jan Holesovsky ke...@suse.cz wrote:
Hi Tobias,
On 2011-01-30 at 20:56 +0100, Tobias Rosenberger wrote:
is there a reason why you don't use git submodule for managing the
other repos in the build repo?
The reason is that so far nobody researched that enough,
15 matches
Mail list logo
