Debian Bug report logs - #576887
git-core: git.el M-x git-status for emacs23

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: submit@bugs.debian.org

Subject: git-core: git.el M-x git-status for emacs23

Date: Thu, 08 Apr 2010 10:55:39 +1000

Package: git-core
Version: 1:1.7.0-1
Severity: normal
File: /etc/emacs/site-start.d/50git-core.el

It'd be good if M-x git-status from
/usr/share/doc/git-core/contrib/emacs/git.el was made available in
emacs23.

If I'm not mistaken it's only vc-git.el in that contrib directory which
emacs23 already has.

I suppose that means having git.el and git-blame.el in a different
directory than vc-git.el.  Symlinking into /usr/share/emacs/site-lisp/
or under a /usr/share/emacs/site-lisp/git-core/ would be one
possibility.  If byte-compiling with an emacsen-install script then
that's a good place to symlink across different files in different emacs
versions (emacs-goodies-el and friends do that I think).

Incidentally, in 50git-core.el it would seem unlikely that every
function in those files should be autoloaded.  Are there just a couple
of user-level interactive entrypoints?  Any elisp program code wanting
the rest ought normally (require 'git) to get them.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 2.6.30-1-486
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages git-core depends on:
ii  libc6                   2.10.1-3         GNU C Library: Shared libraries
ii  libcurl3-gnutls         7.20.0-2         Multi-protocol file transfer libra
ii  libdigest-sha1-perl     2.12-1           NIST SHA-1 message digest algorith
ii  liberror-perl           0.17-1           Perl module for error/exception ha
ii  libexpat1               2.0.1-7          XML parsing C library - runtime li
ii  perl-modules            5.10.1-11        Core Perl modules
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages git-core recommends:
ii  less                          436-1      pager program similar to more
ii  openssh-client [ssh-client]   1:5.3p1-3  secure shell (SSH) client, for sec
ii  patch                         2.6-2      Apply a diff file to an original
ii  rsync                         3.0.7-2    fast remote file copy program (lik

Versions of packages git-core suggests:
pn  git-arch                      <none>     (no description available)
pn  git-cvs                       <none>     (no description available)
pn  git-daemon-run                <none>     (no description available)
ii  git-doc                       1:1.7.0-1  fast, scalable, distributed revisi
pn  git-email                     <none>     (no description available)
pn  git-gui                       <none>     (no description available)
pn  git-svn                       <none>     (no description available)
pn  gitk                          <none>     (no description available)
pn  gitweb                        <none>     (no description available)

-- no debconf information

Message #10 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>, 576887@bugs.debian.org

Cc: emacs23@packages.debian.org, Jari Aalto <jari.aalto@cante.net>

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Wed, 7 Apr 2010 20:42:19 -0500

Hi Kevin,

Kevin Ryde wrote:

> It'd be good if M-x git-status from
> /usr/share/doc/git-core/contrib/emacs/git.el was made available in
> emacs23.
> 
> If I'm not mistaken it's only vc-git.el in that contrib directory which
> emacs23 already has.

I’m not an emacs user, so please forgive my ignorance.  What would be
the pros and cons of what you are suggesting?

I would also be glad to see patches with suggested solutions.  See
/usr/share/doc/git-core/README.source .

> I suppose that means having git.el and git-blame.el in a different
> directory than vc-git.el.  Symlinking into /usr/share/emacs/site-lisp/
> or under a /usr/share/emacs/site-lisp/git-core/ would be one
> possibility.  If byte-compiling with an emacsen-install script then
> that's a good place to symlink across different files in different emacs
> versions (emacs-goodies-el and friends do that I think).
>
> Incidentally, in 50git-core.el it would seem unlikely that every
> function in those files should be autoloaded.  Are there just a couple
> of user-level interactive entrypoints?  Any elisp program code wanting
> the rest ought normally (require 'git) to get them.

I think 50git-core.el does not do anything under Emacs 23.x.
See http://bugs.debian.org/446027

Thanks for the report,
Jonathan

Message #15 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org, emacs23@packages.debian.org, Jari Aalto <jari.aalto@cante.net>

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Sat, 10 Apr 2010 09:46:34 +1000

Jonathan Nieder <jrnieder@gmail.com> writes:
>
> I’m not an emacs user, so please forgive my ignorance.  What would be
> the pros and cons of what you are suggesting?

The pro would be that M-x git-status is automatically available to
emacs23 users.  Done correctly there should be no con.

> I would also be glad to see patches with suggested solutions.  See
> /usr/share/doc/git-core/README.source .

The easiest would be to stick the full pathname in the autoloads.
A byte-compiling install script would be more work but better.

> I think 50git-core.el does not do anything under Emacs 23.x.

Yep, that's the problem. :-)

> See http://bugs.debian.org/446027

Hmm.  That tinytools extraction of all funcs for autoloading seems more
than it needs to be and more than usual for a site-start file.  If
git.el had some ;;;###autoload cookies in it that'd help indicate what
functions it intends to be entrypoints.

Message #20 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org, emacs23@packages.debian.org, Jari Aalto <jari.aalto@cante.net>

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Fri, 9 Apr 2010 22:23:08 -0500

Kevin Ryde wrote:

> The pro would be that M-x git-status is automatically available to
> emacs23 users.  Done correctly there should be no con.

Sounds good to me, so:

> The easiest would be to stick the full pathname in the autoloads.
> A byte-compiling install script would be more work but better.
[...]
> If
> git.el had some ;;;###autoload cookies in it

Go for it.  I suspect Gerrit would be happy (and know I would be happy)
to foist whatever you come up with on the unsuspecting experimental
users, and then we can go from there. :)

Just try it out and send a diff.  If you run into any trouble with
the packaging (like, say, being annoyed with how long it takes to
build the documentation), let me know and I’ll see if I can help.

Cheers,
Jonathan

Message #25 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Mon, 12 Apr 2010 08:30:28 +1000

[Message part 1 (text/plain, inline)]

Jonathan Nieder <jrnieder@gmail.com> writes:
>
> Just try it out and send a diff.

Err, I didn't try a full build, but I get some joy from the files below,
tested in an unpack/repack.

I looked through the long list of startup autoloads and pruned them to
just the entrypoints I could identify.  Can always add back later, but
I'm pretty sure the two left are the only ones that should be there.


For what it's worth I'm not sure how well the code works in emacs21 or
xemacs21, but it byte-compiles successfully so that's enough for the
packaging and can worry later if it needs a bit of help.

[emacsen-startup (text/plain, attachment)]

[emacsen-install (text/plain, attachment)]

[emacsen-remove (text/plain, attachment)]

Message #38 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Sun, 24 Oct 2010 14:19:15 -0500

Kevin Ryde wrote:

>                                     I get some joy from the files below,
> tested in an unpack/repack.

Thank you.  I finally tried the installation, with the following effect:

 Setting up git (1:1.7.2.3-2.1) ...
 Installing new version of config file /etc/emacs/site-start.d/50git-core.el ...
 install/git-core: Handling install of emacsen flavor emacs
 install/git-core: Handling install of emacsen flavor emacs23
 install/git-core: byte-compiling for emacs23
 + emacs23 -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el
 Wrote /usr/share/emacs23/site-lisp/git-core/git.elc

 In git-blame-cleanup:
 git-blame.el:306:6:Warning: `mapcar' called for effect; use `mapc' or `dolist'
     instead

 In git-blame-filter:
 git-blame.el:338:31:Warning: `save-excursion' defeated by `set-buffer'

 In git-blame-create-overlay:
 git-blame.el:386:50:Warning: `save-excursion' defeated by `set-buffer'
 git-blame.el:389:12:Warning: `goto-line' used from Lisp code
 That command is designed for interactive use only

 In end of data:
 git-blame.el:483:1:Warning: the function `format-spec' is not known to be
     defined.
 Wrote /usr/share/emacs23/site-lisp/git-core/git-blame.elc
 + set +x

Does that look right?  How can an emacs newbie like me test it?

Message #43 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Sun, 24 Oct 2010 14:32:48 -0500

Kevin Ryde wrote:

>                                     I get some joy from the files below,

Notes from a quick test (against emacs23 still):

 - I tried M-x git-status from the git package build directory, and it
   produces a nice status display (with debian/files etc as "unknown"
   files).  Now I try "Refresh" from the "Git" menu;
   debian/git/ gets repeated.
   If I try Git → Refresh again, there is yet another debian/git/ line.
   Ideas?

 - M-x git-diff works nicely.

 - In M-x git-blame mode, the left side of each source line does not
   line up unless the author email address is very slow.  Moving around
   does not put a one-line summary anywhere visible on the screen like
   it is advertised to.

Message #48 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org

Subject: Re: Bug#576887: git-core: git.el M-x git-status for emacs23

Date: Sun, 24 Oct 2010 14:42:01 -0500

Jonathan Nieder wrote:

>  - In M-x git-blame mode, the left side of each source line does not
>    line up unless the author email address is very slow

By "slow", I mean "short".

Example:

	850235     <junkio@cox.net>:#include "builtin.h"
	2b11e3 <Johannes.Schindelin@gmx.de>:#include "cache.h"
	fd5c36 <tfransosi@gmail.com>:#include "exec_cmd.h"
	fd5c36 <tfransosi@gmail.com>:#include "help.h"
	575ba9     <matled@gmx.net>:#include "quote.h"
	d8e96f      <peff@peff.net>:#include "run-command.h"
	8e49d5        <exon@op5.se>:
	822a7d <ramsay@ramsay1.demon.co.uk>>:const char git_usage_string[] =

Sorry for the nonsense.

Message #53 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Fri, 29 Oct 2010 08:38:25 +1100

Jonathan Nieder <jrnieder@gmail.com> writes:
>
>  In end of data:
>  git-blame.el:483:1:Warning: the function `format-spec' is not known to be
>      defined.

I think that one may be my bug 577471.

(I still don't know how it could have been like that, unless all git
users always load up format-spec.el too.  Gnus might use it, so maybe
that's why :-).

Message #58 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Thu, 28 Oct 2010 16:46:00 -0500

Kevin Ryde wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:

>>  In end of data:
>>  git-blame.el:483:1:Warning: the function `format-spec' is not known to be
>>      defined.
>
> I think that one may be my bug 577471.

Ah, okay.  I'll bug the list. :)

> (I still don't know how it could have been like that, unless all git
> users always load up format-spec.el too.  Gnus might use it, so maybe
> that's why :-).

Thanks for the hint; makes sense.

Message #63 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Fri, 29 Oct 2010 08:46:26 +1100

Jonathan Nieder <jrnieder@gmail.com> writes:
>
>  In git-blame-cleanup:
>  git-blame.el:306:6:Warning: `mapcar' called for effect; use `mapc' or `dolist'
>      instead

True but not very important.

>  In git-blame-filter:
>  git-blame.el:338:31:Warning: `save-excursion' defeated by `set-buffer'
>  In git-blame-create-overlay:
>  git-blame.el:386:50:Warning: `save-excursion' defeated by `set-buffer'

Maybe should be `with-current-buffer' per the elisp manual example.
I hadn't noticed any obvious ill effect, but I don't think I tried it
much.

>  git-blame.el:389:12:Warning: `goto-line' used from Lisp code
>  That command is designed for interactive use only

True but not fatal.  I see the `goto-line' docstring recommends
`forward-line'.

Message #68 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Fri, 29 Oct 2010 08:57:20 +1100

Jonathan Nieder <jrnieder@gmail.com> writes:
>
>    Now I try "Refresh" from the "Git" menu;
>    debian/git/ gets repeated.

Not quite sure what you mean but the very simple uses I've put it to
have seemed ok for me on refreshing (though the "g" key normally, if
that makes a difference).

>  - In M-x git-blame mode, the left side of each source line does not
>    line up

The %20A in git-blame-prefix-format may mean only 20 columns for the
author.  I expect that can be customized.

(Or is there a way to abbreviate long authors?  Could be a cute feature
for format-spec.el itself to have, either a truncate or ellipsise or
whatever.)

Message #73 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Kevin Ryde <user42@zip.com.au>

Cc: 576887@bugs.debian.org, David Kågedal <davidk@lysator.liu.se>, Sergei Organov <osv@javad.com>, Andreas Schwab <schwab@linux-m68k.org>

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Mon, 8 Nov 2010 02:31:08 -0600

Hi again,

Kevin Ryde wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:

>>  In git-blame-cleanup:
>>  git-blame.el:306:6:Warning: `mapcar' called for effect; use `mapc' or `dolist'
>>      instead
>
> True but not very important.
>
>>  In git-blame-filter:
>>  git-blame.el:338:31:Warning: `save-excursion' defeated by `set-buffer'
>>  In git-blame-create-overlay:
>>  git-blame.el:386:50:Warning: `save-excursion' defeated by `set-buffer'
>
> Maybe should be `with-current-buffer' per the elisp manual example.
> I hadn't noticed any obvious ill effect, but I don't think I tried it
> much.
>
>>  git-blame.el:389:12:Warning: `goto-line' used from Lisp code
>>  That command is designed for interactive use only
>
> True but not fatal.  I see the `goto-line' docstring recommends
> `forward-line'.

Thanks for the analysis.  In order to

 1) suppress these warnings when the elisp is compiled,
  and
 2) make sure git's emacs support is not broken by a random
    future emacs upgrade

I think it is worth fixing these.  Any pointers?  How can one retrieve
elisp docstrings, and is there a postscript or HTML reference manual?

Thanks again for all the help.  I don't know what I'd do without it.
Jonathan

Message #78 received at 576887@bugs.debian.org (full text, mbox, reply):

From: Kevin Ryde <user42@zip.com.au>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 576887@bugs.debian.org, David Kågedal <davidk@lysator.liu.se>, Sergei Organov <osv@javad.com>, Andreas Schwab <schwab@linux-m68k.org>

Subject: Re: git-core: git.el M-x git-status for emacs23

Date: Tue, 09 Nov 2010 07:58:57 +1100

Jonathan Nieder <jrnieder@gmail.com> writes:
>
>  1) suppress these warnings when the elisp is compiled,

Sometimes more trouble than its worth :-).

> How can one retrieve
> elisp docstrings, and is there a postscript or HTML reference manual?

Package emacs23-common-non-dfsg, but, umm, you might want to be a bit
careful before diving into that filter bit.  Doesn't look hard but may
have to watch out for what if anything is supposed to happen to point.

(A bit more important one is my bug 577834 which gets an actual error if
you don't want font-lock fruit salad turned on.)


-- 
The Copenhagen Interpretation elucidated for the layman:
You can't know for sure until you see for yourself.

Message #99 received at 576887-close@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: 576887-close@bugs.debian.org

Subject: Bug#576887: fixed in git 1:1.7.4.1-1

Date: Thu, 17 Feb 2011 12:17:30 +0000

Source: git
Source-Version: 1:1.7.4.1-1

We believe that the bug you reported is fixed in the latest version of
git, which is due to be installed in the Debian FTP archive:

git-all_1.7.4.1-1_all.deb
  to main/g/git/git-all_1.7.4.1-1_all.deb
git-arch_1.7.4.1-1_all.deb
  to main/g/git/git-arch_1.7.4.1-1_all.deb
git-core_1.7.4.1-1_all.deb
  to main/g/git/git-core_1.7.4.1-1_all.deb
git-cvs_1.7.4.1-1_all.deb
  to main/g/git/git-cvs_1.7.4.1-1_all.deb
git-daemon-run_1.7.4.1-1_all.deb
  to main/g/git/git-daemon-run_1.7.4.1-1_all.deb
git-doc_1.7.4.1-1_all.deb
  to main/g/git/git-doc_1.7.4.1-1_all.deb
git-email_1.7.4.1-1_all.deb
  to main/g/git/git-email_1.7.4.1-1_all.deb
git-gui_1.7.4.1-1_all.deb
  to main/g/git/git-gui_1.7.4.1-1_all.deb
git-man_1.7.4.1-1_all.deb
  to main/g/git/git-man_1.7.4.1-1_all.deb
git-svn_1.7.4.1-1_all.deb
  to main/g/git/git-svn_1.7.4.1-1_all.deb
git_1.7.4.1-1.diff.gz
  to main/g/git/git_1.7.4.1-1.diff.gz
git_1.7.4.1-1.dsc
  to main/g/git/git_1.7.4.1-1.dsc
git_1.7.4.1.orig.tar.gz
  to main/g/git/git_1.7.4.1.orig.tar.gz
gitk_1.7.4.1-1_all.deb
  to main/g/git/gitk_1.7.4.1-1_all.deb
gitweb_1.7.4.1-1_all.deb
  to main/g/git/gitweb_1.7.4.1-1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 576887@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan Nieder <jrnieder@gmail.com> (supplier of updated git package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 15 Feb 2011 19:27:38 -0600
Source: git
Binary: git git-man git-core git-doc git-arch git-cvs git-svn git-email git-daemon-run git-gui gitk gitweb git-all
Architecture: all source
Version: 1:1.7.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Gerrit Pape <pape@smarden.org>
Changed-By: Jonathan Nieder <jrnieder@gmail.com>
Description: 
 git        - fast, scalable, distributed revision control system
 git-all    - fast, scalable, distributed revision control system (all subpacka
 git-arch   - fast, scalable, distributed revision control system (arch interop
 git-core   - fast, scalable, distributed revision control system (obsolete)
 git-cvs    - fast, scalable, distributed revision control system (cvs interope
 git-daemon-run - fast, scalable, distributed revision control system (git-daemon s
 git-doc    - fast, scalable, distributed revision control system (documentatio
 git-email  - fast, scalable, distributed revision control system (email add-on
 git-gui    - fast, scalable, distributed revision control system (GUI)
 git-man    - fast, scalable, distributed revision control system (manual pages
 git-svn    - fast, scalable, distributed revision control system (svn interope
 gitk       - fast, scalable, distributed revision control system (revision tre
 gitweb     - fast, scalable, distributed revision control system (web interfac
Closes: 465776 466471 499002 507476 524309 540001 575917 576887 577471 578752 581691 583693 583699 585725 588103 598245 600566 600785 606975 607044 610423 610481 611608
Changes: 
 git (1:1.7.4.1-1) unstable; urgency=low
 .
   * new upstream release (closes: #600566, #575917, #578752, #583693,
     #583699, #588103, #507476, #540001, #524309, #581691, #600785,
     #577471, #607044, #606975, #610423, #610481).
 .
   [ Anders Kaseorg ]
   * debian/git.docs, debian/rules: deal with RelNotes subdirectory.
   * debian/diff/0007-gitk-Take-only-numeric-...diff: new; gitk: do
     not error out when git version number contains "-rc".
 .
   [ Jonathan Nieder ]
   * add myself as uploader.
   * debian/diff/0003, 0007, 0010-0034: remove, applied upstream.
   * debian/rules: accept patches with .patch suffix, too (thx Anders
     Kaseorg).
   * debian/rules: use patch -N -r- so patch application is idempotent.
   * update debian/copyright.
   * debian/diff/0001-ident-check-etc-mailname...diff: avoid calls to
     gethostbyname when mailname is not an fqdn (closes: #611608).
   * debian/diff/0005-gitk-use-...diff: new; gitk: use standard desktop
     fonts by default.  The appearance for users that already have a
     generated ~/.gitk file is not affected (closes: #466471).
   * debian/diff/0006-gitk-...diff: new; gitk: avoid spurious matches
     in "All fields" search (thx Frédéric Brière, closes: #465776).
   * debian/control: git-cvs: recommend cvs2git for one-time conversions
     (closes: #585725).
   * debian/control: git-core: explain that it still may be needed (thx
     Denis Laxalde).
   * debian/control: gitweb: allow lynx-cur to satisfy dependency on a
     CGI implementation (thx Ivan Shmakov).
   * debian/control, debian/rules: new architecture-independent package
     git-man: manual pages that were previously in the main git package.
   * debian/rules: do not build documentation on autobuilders (closes:
     #499002).
   * debian/control: Build-Depends-Indep: asciidoc, xmlto, docbook-xsl.
   * debian/rules: git-gui: install git-gui--askpass helper to
     /usr/lib/git-core (closes: #598245).
   * debian/rules: git-doc: install symlink to html documentation in
     /usr/share/doc/git (thx Ian Jackson).
   * debian/watch: new; point to upstream sources.
   * debian/implicit: create DEBIAN/md5sums with correct permissions.
   * debian/diff/0003-remove-shebang...diff: new; do not start shell
     libraries with #!/bin/sh.
   * debian/rules: do not try to strip scripts even if they begin
     with "# " in place of "#!".
   * debian/diff/0004-pre-rebase-hook-capture...diff: new;
     hooks/pre-rebase: use a <<HERE document to prevent syntax checkers
     from treating documentation as code.
   * debian/implicit: check for debian/$pkg.doc-base.$docid.
   * debian/git-doc.doc-base.*: new; catalog provided documentation.
   * debian/implicit: check for debian/$pkg.lintian-overrides.
   * debian/git.lintian-overrides: new; document some deviations from
     lintian guidelines.
   * debian/control: Standards-Version: 3.9.1.0.
 .
   * debian/git.README.Debian: server logs go in /var/log/apache2.
   * debian/diff/0002-Revert-Merge-branch-jn-gitweb...diff: remove.
   * debian/diff/0006, 0008, 0009-instaweb...diff: remove, no longer
     needed.
   * debian/rules, debian/control: move gitweb script to the main git
     package for use by instaweb; make gitweb into a configuration
     package.
   * debian/gitweb.NEWS.Debian, debian/git.README.Debian,
     debian/gitweb.conf: static files moved to /usr/share/gitweb/static.
   * debian/gitweb.conf: disable rename patches (@diff_opts = ()).
   * debian/diff/0001-Revert-gitweb-...diff: remove; no longer needed.
   * debian/rules: gitweb: move gitweb.cgi script to /usr/share;
     add a symlink at /usr/lib/cgi-bin/gitweb.cgi for compatibility.
 .
   * debian/git.emacsen-install, debian/rules, debian/git.postinst,
     debian/git.prerm: put emacs support files in /usr/share/git-core
     instead of /usr/share/doc/git/contrib.
   * debian/implicit: check for arbitrary debian/$pkg.README.*, not just
     README.source and README.Debian.
   * debian/git.README.emacs: new; introduction to the emacs support
     (text taken from contrib/emacs/README).
 .
   [ Kevin Ryde ]
   * debian/rules, debian/git.emacsen-*, debian/git.postinst,
     debian/git.prerm: Make M-x git-status and git-blame modes available
     with emacs23 (closes: #576887).
Checksums-Sha1: 
 454abccda82b0e5ae7d82c60df95f5fe30d51e69 1436 git_1.7.4.1-1.dsc
 2c9c9ac6dd6ae284df2282bb0c4145c0ae0e7e35 3266745 git_1.7.4.1.orig.tar.gz
 a2cdc8ed70b6c7b7c81050db851eed4ae7c46d98 402484 git_1.7.4.1-1.diff.gz
 96abd1b428884ff1658e25460c78990f249dd566 1639718 git-doc_1.7.4.1-1_all.deb
 6c4e9a61f6e7e50e626ad6666863eb14aa3115f3 386026 git-arch_1.7.4.1-1_all.deb
 452028cba6abaa84d5f3cdf94402d5a6b47455d8 457992 git-cvs_1.7.4.1-1_all.deb
 1aa1567131b1f52c30b43b9e9954afb1dd56a9d7 437754 git-svn_1.7.4.1-1_all.deb
 c1810309d276d79e3899ac85c9ff8dc022ee89b0 373080 git-daemon-run_1.7.4.1-1_all.deb
 e0500154020a1339bbab0d7db6af8d356676540b 390972 git-email_1.7.4.1-1_all.deb
 49b76d65cc7c06a16a9c80931b2eccd7d4f7a241 633922 git-gui_1.7.4.1-1_all.deb
 c5da6c0326defee5a2772b32f9c2b529757ea555 498734 gitk_1.7.4.1-1_all.deb
 4aa64839c62ac780e1e0c3720ac678e7733f3286 383134 gitweb_1.7.4.1-1_all.deb
 397d1bb3abf61e4f43951f5b8ad4574e31ddc16e 371460 git-all_1.7.4.1-1_all.deb
 ffd6bd7b39b91dd66c5d2b98239492a826cbee9e 1336 git-core_1.7.4.1-1_all.deb
 5c133d9d1654d094463e0fddba797de60b1d2e0e 938934 git-man_1.7.4.1-1_all.deb
Checksums-Sha256: 
 ac242c36ec673683dc6a165ea15ab4659924c90a97ccaa0d53000966a691a2b0 1436 git_1.7.4.1-1.dsc
 1855df9f23f8296c24482416cf10bbbaef40f837d30ff02ecf31f2694c325277 3266745 git_1.7.4.1.orig.tar.gz
 bfd435ff77f364ac4e6054b8506e2b110703aa53675091b72557dcf943e962b2 402484 git_1.7.4.1-1.diff.gz
 46cd7b1ed2338f34ea44ad0b336941d5713be0277300681f3140fecc853483c6 1639718 git-doc_1.7.4.1-1_all.deb
 65318f6f273c516cbb885dcd8674c66be1487209d283ea73816988acf4ac5c9c 386026 git-arch_1.7.4.1-1_all.deb
 296f41e0b8deeec79f53ce8a11524b6714a6711bcbe08c02c01843e666d5faed 457992 git-cvs_1.7.4.1-1_all.deb
 0633ba3b3a9e390ce0b7f2a443f3f717772ae2e62fe0f9497078f080a8dc02f2 437754 git-svn_1.7.4.1-1_all.deb
 85a7a8a4e9cfe1ec18dfceb5207b39794a62e35fe91af7d7bb4dd848eaa98f52 373080 git-daemon-run_1.7.4.1-1_all.deb
 f470ce38eba3671ba46103289e2a15274610cb8d6698357ee402637f8bde25f8 390972 git-email_1.7.4.1-1_all.deb
 662393f15a90faf0749982afcddd9bc393b38acca1fe8fe1f57b6fab11fa8bd4 633922 git-gui_1.7.4.1-1_all.deb
 9d40ff6646ae2f1898a9bdef0e3fdebecea3ae2ed8925ac9a458f3e5e3649843 498734 gitk_1.7.4.1-1_all.deb
 dec1a6dd4db7e572bb7c54b5774b3d3b67ddbdbc2472dbd609e82e72bbc88013 383134 gitweb_1.7.4.1-1_all.deb
 65609c1132f1a11330c50ecfc4b3ab7dc9a0c87ad96991bdfd9f7c4852f41c98 371460 git-all_1.7.4.1-1_all.deb
 ac6b3f5d86005b49957b6a6f3ffe4c403bdc41f47ccf811f6f9b735bff17bf99 1336 git-core_1.7.4.1-1_all.deb
 2a4ec7d8c40ef8cfc1c107de1df99ababddfa77634e98ca1b2ef8bd54ed961b3 938934 git-man_1.7.4.1-1_all.deb
Files: 
 19aec48a88c642f378a9933a504fcab5 1436 vcs optional git_1.7.4.1-1.dsc
 1276aa1366bd3c670e9c51f1bff12f36 3266745 vcs optional git_1.7.4.1.orig.tar.gz
 36e04488680d57b513ac3b840844b94a 402484 vcs optional git_1.7.4.1-1.diff.gz
 e7f79fd736d1c476383c52d1cd19496d 1639718 doc optional git-doc_1.7.4.1-1_all.deb
 760acf52d5a99ed3fd19178f23372f41 386026 vcs optional git-arch_1.7.4.1-1_all.deb
 0dd4d96de84ab8ee6e7fc275430ab49e 457992 vcs optional git-cvs_1.7.4.1-1_all.deb
 bbe84f5bb1724082834313cdff3a9cff 437754 vcs optional git-svn_1.7.4.1-1_all.deb
 499ea96dbd14deccac0a089c03921779 373080 vcs optional git-daemon-run_1.7.4.1-1_all.deb
 0cfb71b4f253fe88269d76b710ce2462 390972 vcs optional git-email_1.7.4.1-1_all.deb
 04535918668f71bea565ae7496590254 633922 vcs optional git-gui_1.7.4.1-1_all.deb
 a2156ce5c0a15aacdb9df7ae63999703 498734 vcs optional gitk_1.7.4.1-1_all.deb
 d3aaef1ded07729024375a9bf1f8e2a1 383134 vcs optional gitweb_1.7.4.1-1_all.deb
 e84c9ac9452c37e6011ffc48ca053711 371460 vcs optional git-all_1.7.4.1-1_all.deb
 5ccaeef1abbb1debf65c09766c2ff86c 1336 vcs optional git-core_1.7.4.1-1_all.deb
 28d0be6d985e3f9bf8071601a6c1c6bf 938934 vcs optional git-man_1.7.4.1-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk1bqScACgkQGJoyQbxwpv/CiACgidlYAgvKP9U626u4US+/jj1p
4qQAni2trKCqN6+c4N2F/gOvbJU5hgIb
=aIcU
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.