git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Petr Stodulka <pstodulk@redhat.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: Forgotten declaration of function path_name() in revision.h?
Date: Wed, 16 Mar 2016 14:48:53 -0400	[thread overview]
Message-ID: <20160316184853.GA32615@sigill.intra.peff.net> (raw)
In-Reply-To: <56E9A07D.3080508@redhat.com>

On Wed, Mar 16, 2016 at 07:05:49PM +0100, Petr Stodulka wrote:

> according to commit 9831e92 (merge) there is maybe by mistake kept declaration
> of function path_name() in revision.h, whose definition was removed
> and isn't used in git anymore.

Yes, this should have been part of de1e67d (list-objects: pass full
pathname to callbacks, 2016-02-11), but I missed it.

The patch itself looks fine to me (though it probably makes more sense
to point to de1e67d than the merge).

Note also that:

> ======================================================================
> From ae72c8f9085b3b7bd84f94f90ff5b0416db59d67 Mon Sep 17 00:00:00 2001
> From: Petr Stodulka <pstodulk@redhat.com>
> Date: Wed, 16 Mar 2016 18:51:53 +0100
> Subject: [PATCH] remove obsoleted function path_name() from header file
>  revision.h

It makes things easier on the maintainer if you format your patch such
that "git am" can apply it directly. Use scissors like:

-- >8 --

to separate the patch from anything that should not go into the commit
message (rather than "=====..." as you have here).

Drop the "From " line which says nothing (it is an mbox separator, but
we are already inside a message).

The rest of the headers do not hurt, but are generally redundant with
what is in your email header (though in this case, the Subject is
different, so you would want to retain that).

-Peff

  reply	other threads:[~2016-03-16 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 18:05 Forgotten declaration of function path_name() in revision.h? Petr Stodulka
2016-03-16 18:48 ` Jeff King [this message]
2016-03-16 18:52   ` Eric Sunshine
2016-03-16 19:08   ` Petr Stodulka

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

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

  git send-email \
    --in-reply-to=20160316184853.GA32615@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pstodulk@redhat.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.
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 NNTP newsgroup(s).