* Working on master and branch_release-1-8 in the same repository
@ 2008-06-09 20:59 Neil Jerram
2008-06-10 7:40 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: Neil Jerram @ 2008-06-09 20:59 UTC (permalink / raw)
To: guile-devel
I find that when switching from master to branch_release-1-8, I
usually need to do a complete rebuild (i.e. make distclean, autogen,
configure, make, make check). Do others find this too, or is there
something clever I can do to avoid it and still be sure that I'm
getting correct builds?
Thanks,
Neil
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Working on master and branch_release-1-8 in the same repository
2008-06-09 20:59 Working on master and branch_release-1-8 in the same repository Neil Jerram
@ 2008-06-10 7:40 ` Ludovic Courtès
2008-06-19 13:25 ` Neil Jerram
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2008-06-10 7:40 UTC (permalink / raw)
To: guile-devel
Hi,
"Neil Jerram" <neiljerram@googlemail.com> writes:
> I find that when switching from master to branch_release-1-8, I
> usually need to do a complete rebuild (i.e. make distclean, autogen,
> configure, make, make check). Do others find this too, or is there
> something clever I can do to avoid it and still be sure that I'm
> getting correct builds?
I use `ccache', which helps reduce the time needed to recompile.
I found that, for some reason, running `autoreconf' is only needed when
switching from 1.8 to `master', otherwise a failure is hit in
`socket.test', typically.
Of course, another solution is to store each branch in a separate
directory.
Thanks,
Ludo'.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Working on master and branch_release-1-8 in the same repository
2008-06-10 7:40 ` Ludovic Courtès
@ 2008-06-19 13:25 ` Neil Jerram
2008-06-23 12:30 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: Neil Jerram @ 2008-06-19 13:25 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guile-devel
2008/6/10 Ludovic Courtès <ludo@gnu.org>:
> Hi,
>
> "Neil Jerram" <neiljerram@googlemail.com> writes:
>
>> I find that when switching from master to branch_release-1-8, I
>> usually need to do a complete rebuild (i.e. make distclean, autogen,
>> configure, make, make check). Do others find this too, or is there
>> something clever I can do to avoid it and still be sure that I'm
>> getting correct builds?
>
> I use `ccache', which helps reduce the time needed to recompile.
Thanks, that looks interesting, I'll try it.
> Of course, another solution is to store each branch in a separate
> directory.
Do you mean as separate (cloned) Git repositories? If not, what
exactly do you mean?
Regards,
Neil
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Working on master and branch_release-1-8 in the same repository
2008-06-19 13:25 ` Neil Jerram
@ 2008-06-23 12:30 ` Ludovic Courtès
2008-06-23 22:48 ` Neil Jerram
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2008-06-23 12:30 UTC (permalink / raw)
To: guile-devel
Hello,
"Neil Jerram" <neiljerram@googlemail.com> writes:
> 2008/6/10 Ludovic Courtès <ludo@gnu.org>:
>> Of course, another solution is to store each branch in a separate
>> directory.
>
> Do you mean as separate (cloned) Git repositories?
Yes. Either cloned from the Savannah repository, or mutually cloned.
This is what one typically does when using CVS/SVN, but it requires more
disk space.
Thanks,
Ludovic.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-06-23 22:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-09 20:59 Working on master and branch_release-1-8 in the same repository Neil Jerram
2008-06-10 7:40 ` Ludovic Courtès
2008-06-19 13:25 ` Neil Jerram
2008-06-23 12:30 ` Ludovic Courtès
2008-06-23 22:48 ` Neil Jerram
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).