git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stefan Zager <szager@google.com>
Cc: Chris Packham <judge.packham@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Make the global packed_git variable static to sha1_file.c.
Date: Wed, 12 Feb 2014 19:53:12 +0100	[thread overview]
Message-ID: <87txc488o7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAHOQ7J-2BkQOr+_BF42ja4pWaUWkt8OC-YE0ETwHAYsmrubi=A@mail.gmail.com> (Stefan Zager's message of "Wed, 12 Feb 2014 10:26:22 -0800")

Stefan Zager <szager@google.com> writes:

> On Tue, Feb 11, 2014 at 11:29 PM, Chris Packham <judge.packham@gmail.com> wrote:
>> Hi,
>>
>> On 12/02/14 14:57, Stefan Zager wrote:
>>> From b4796d9d99c03b0b7cddd50808a41413e45f1129 Mon Sep 17 00:00:00 2001
>>> From: Stefan Zager <szager@chromium.org>
>>> Date: Mon, 10 Feb 2014 16:55:12 -0800
>>> Subject: [PATCH] Make the global packed_git variable static to sha1_file.c.
>>
>> I'm not really qualified to comment on substance but there are some
>> basic style issues w.r.t. whitespace namely using 4 spaces for indent
>> and mixing tabs/spaces. This might seem pedantic for the first round of
>> a patch but it does put off reviewers.
>>
>> From Documentation/CodingGuidelines:
>>
>>  - We use tabs to indent, and interpret tabs as taking up to
>>    8 spaces.
>
> My bad, I will upload a fixed patch.  In my defense: I edited the code
> in emacs and then ran "M-x tabify" over the entire file.  But that had
> the unfortunate side effect of adding a bunch of whitespace-only
> changes to the diff, illuminating the fact that there is already mixed
> whitespace in the existing code.  So I had to go back and selectively
> tabify my changes, and I clearly missed a bunch.
>
> If anyone has a recommendation for a less labor-intensive way to do
> this in emacs, I'd be very grateful.

C-c . RET linux RET before entering any changes.

-- 
David Kastrup

  reply	other threads:[~2014-02-12 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  1:57 [PATCH] Make the global packed_git variable static to sha1_file.c Stefan Zager
2014-02-12  7:29 ` Chris Packham
2014-02-12 18:26   ` Stefan Zager
2014-02-12 18:53     ` David Kastrup [this message]
2014-02-12 19:28     ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2014-02-13 23:09 szager

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87txc488o7.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=judge.packham@gmail.com \
    --cc=szager@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).