[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gimp-print-devel
Subject:    Re: [Gimp-print-devel] ANNOUNCE: Gutenprint 5.1.0 and 5.0.0.99.1
From:       Robert L Krawitz <rlk () alum ! mit ! edu>
Date:       2007-03-05 0:17:53
Message-ID: 200703050017.l250HrLO028399 () dsl092-065-009 ! bos1 ! dsl ! speakeasy ! net
[Download RAW message or body]

   Date: Mon, 05 Mar 2007 00:08:04 +0000
   From: Till Kamppeter <till.kamppeter@gmail.com>

   Everything which was missing I have updated now, in both branches.

   One remark: You mistyped the branch name. Correct is
   "gutenprint-5_0-branch".

Happens.

   It is possible that I have also updated obsolete files, but this way
   getting old stuff back in via cut & paste is avoided.

That's fine.

   Robert L Krawitz wrote:
   >    Date: Sun, 04 Mar 2007 22:04:57 +0000
   >    From: Till Kamppeter <till.kamppeter@gmail.com>
   >    Cc: gimp-print-devel@lists.sourceforge.net
   > 
   >    Robert L Krawitz wrote:
   >    >    Date: Sun, 04 Mar 2007 14:38:40 +0000
   >    >    From: Till Kamppeter <till.kamppeter@gmail.com>
   >    > 
   >    >    Most documentation/NEWS/README files, debian/control, files in
   >    >    src/foomatic/ (comments at the head of the file). The PDF manual (needs
   >    >    to be fixed in the source file and rebuilt).
   >    > 
   >    > I only found a handful of things.  Could you find the specific issues
   >    > and fix them?  I believe you have developer CVS access.
   > 
   >    I have developer access, but due to not knowing the branch name of the
   >    stable release I could only work on the HEAD branch. There are two files
   >    which still contained linuxprinting:
   > 
   > gutenprint-5_0_branch (you can figure this out via cvs log).
   > 
   >    doc/gutenprint-users-manual.pdf
   >    doc/users_guide/title.sgml
   > 
   > I've fixed the user's manual (based on the .odt file) on the mainline,
   > but haven't back ported it to the branch yet.
   > 
   >    The sgml file I have fixed and committed. Can you regenerate and
   >    commit the PDF? The OpenOffice file seems to be the source of it
   >    and that one is up to date.
   > 
   > Actually, I don't think we're even distributing the old user's guide
   > (which is based on 4.2) any more.
   > 
   >    Can you tell me the branch name of the stable branch, as on
   >    SourceForge you cannot browse the repositories already for years
   >    and they will probably never fix it. Or do you know a secret URL
   >    for browsing the repositories?
   > 
   > Well, if you're able to commit stuff via CVS, you can use the normal
   > cvs commands, such as cvs log.
   > 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
[prev in list] [next in list] [prev in thread] [next in thread]