Re: Updated handling of the git repositories

Thorsten Behrens <[email protected]> Sat, 4 Sep 2010 22:15:21 +0200
Newsgroups gmane.comp.gnome.ximian.openoffice
Message-ID <[email protected]>
--===============1777458734==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g"
Content-Disposition: inline


--2fHTh5uZTiUOsy+g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

To Jan Holesovsky wrote:
> > That way, I'd just hardcode the git-new-workdir into download.in (I
> > mean, test for the leading '/' there, and decide the action), so that it
> > can be announced appropriately, does not have to be brought in through
> > autoconf etc.
> >=20
> yeah, if it's acceptable for everyone - let's move much of the logic
> into download.in.
>=20
Pushed. Logic slightly less lame than before, now checks for OOO_GIT
holding valid dir, and then going for git-new-workdir.

Cheers,

-- Thorsten

--2fHTh5uZTiUOsy+g
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEARECAAYFAkyCqNkACgkQ0atnB9QI2h8OHwCgh79+mKxylsH/gH9Ab7jMrgrM
tCMAnRoqTcbjrMOMH+SbN7D3QxG5j7gh
=5xQb
-----END PGP SIGNATURE-----

--2fHTh5uZTiUOsy+g--

--===============1777458734==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline