On Thu, 16 Sep 2010, Chris Baines wrote:
> I am looking for a sponsor or many sponsors for my new and updated
> FlightGear related packages. I have included a summary of all the
> information in one email to make it easier to read and understand.
>
> The updated packages are "flightgear", "fgfs-b
Dear mentors,
I am looking for a sponsor or many sponsors for my new and updated
FlightGear related packages. I have included a summary of all the
information in one email to make it easier to read and understand.
The updated packages are "flightgear", "fgfs-base" and "simgear", all
moving to th
Goswin von Brederlow writes:
> I'm afraid not, other than have libopensync1 change the library name so
> it has libopensync1.so or something.
Please no!
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the
On Thu, 16 Sep 2010 19:00:27 +1000
Matthew Palmer wrote:
> > > On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote:
> > > > Why won't you just use `git --describe`?
> > > > It produces nice version numbers of the format
> > > > --
> > > > (or just when you're packaging a release)
>
>
On Thu, Sep 16, 2010 at 09:59:43AM +0200, Adam Borowski wrote:
> On Thu, Sep 16, 2010 at 03:22:31PM +1000, Matthew Palmer wrote:
> > On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote:
> > > Why won't you just use `git --describe`?
> > > It produces nice version numbers of the format
> >
On Thu, Sep 16, 2010 at 03:22:31PM +1000, Matthew Palmer wrote:
> On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote:
> > Why won't you just use `git --describe`?
> > It produces nice version numbers of the format
> > --
> > (or just when you're packaging a release)
> >
> > The "start
6 matches
Mail list logo