git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Benoit SIGOURE <tsuna@lrde.epita.fr>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git list <git@vger.kernel.org>
Subject: Re: [PATCHv2 1/5] Add a generic tree traversal to fetch SVN properties.
Date: Tue, 16 Oct 2007 17:10:29 +0200	[thread overview]
Message-ID: <0D1ADA80-223C-4143-BCEC-5275E0EAD357@lrde.epita.fr> (raw)
In-Reply-To: <4714D068.8090606@viscovery.net>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Oct 16, 2007, at 4:53 PM, Johannes Sixt wrote:

> Benoit Sigoure schrieb:
>> 	* git-svn.perl (&traverse_ignore): Remove.
>> 	(&prop_walk): New.
>> 	(&cmd_show_ignore): Use prop_walk.
>
> This may be your favorite style of commit messaged, but I think the  
> concensus for git is a different style of commit message: We would  
> like to see *why* this change is good. But you only note *what* was  
> changed, something that can be seen by looking at the patch anyway.
>
> The commit message should be helpful when the commit is looked at  
> in isolation, like when you are doing some code archeology half a  
> year later and e.g. git-blame/git-bisect points you to this commit.
>
> Also a notice such as
>
>  "With this we will be able to lift properties like svn:ignore into
>   .gitignore in a follow-up change."
>
> tells that this was actually part of a series and you don't have to  
> remember that half a year ago there were 4 more patches submitted  
> in the same second with this one.

Indeed, sorry, I'll write more explanatory commit messages next time :)

-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

      reply	other threads:[~2007-10-16 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 14:36 [PATCHv2 1/5] Add a generic tree traversal to fetch SVN properties Benoit Sigoure
2007-10-16 14:36 ` [PATCHv2 2/5] Implement git svn create-ignore Benoit Sigoure
2007-10-16 14:36   ` [PATCHv2 3/5] Add git svn propget Benoit Sigoure
2007-10-16 14:36     ` [PATCHv2 4/5] Add git svn proplist Benoit Sigoure
2007-10-16 14:36       ` [PATCHv2 5/5] Simplify the handling of fatal errors Benoit Sigoure
2007-11-12 17:13       ` [PATCH] git-svn: Document the `create-ignore', `propget' and `proplist' subcommands Benoit Sigoure
2007-10-16 14:53 ` [PATCHv2 1/5] Add a generic tree traversal to fetch SVN properties Johannes Sixt
2007-10-16 15:10   ` Benoit SIGOURE [this message]

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=0D1ADA80-223C-4143-BCEC-5275E0EAD357@lrde.epita.fr \
    --to=tsuna@lrde.epita.fr \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /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).