git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Ericsson <ae@op5.se>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix references to deprecated commands
Date: Mon, 12 Nov 2007 10:37:19 +0100	[thread overview]
Message-ID: <20071112093719.GA22555@diku.dk> (raw)
In-Reply-To: <7vbq9z50vj.fsf@gitster.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> wrote Mon, Nov 12, 2007:
> Jonas Fonseca <fonseca@diku.dk> writes:
> 
> > diff --git a/Documentation/git-get-tar-commit-id.txt b/Documentation/git-get-tar-commit-id.txt
> > index 9b5f86f..ef1b19c 100644
> > --- a/Documentation/git-get-tar-commit-id.txt
> > +++ b/Documentation/git-get-tar-commit-id.txt
> > @@ -14,12 +14,12 @@ SYNOPSIS
> >  DESCRIPTION
> >  -----------
> >  Acts as a filter, extracting the commit ID stored in archives created by
> > -git-tar-tree.  It reads only the first 1024 bytes of input, thus its
> > +gitlink:git-archive[1].  It reads only the first 1024 bytes of input, thus its
> >  runtime is not influenced by the size of <tarfile> very much.
> >  
> >  If no commit ID is found, git-get-tar-commit-id quietly exists with a
> >  return code of 1.  This can happen if <tarfile> had not been created
> > -using git-tar-tree or if the first parameter of git-tar-tree had been
> > +using git-archive or if the <treeish> parameter of git-archive had been
> >  a tree ID instead of a commit ID or tag.
> >
> > -- 
> > Jonas Fonseca
> 
> How did you prepare this hunk?  I count 10 lines preimage and
> postimage, followed by a blank line and the signature separator
> "-- " you added in your MUA, but the header claims to have 12
> lines.

I am sorry to cause you this kind of problems. Usually I keep the patch
ending inserted by format-patch, but yesterday I deleted it for some
unknown reason. Maybe I should learn to use git-send-email. 

-- 
Jonas Fonseca

  reply	other threads:[~2007-11-12  9:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 22:54 [PATCH] Deprecate git-lost-found Johannes Schindelin
2007-11-08  0:19 ` Junio C Hamano
2007-11-08  0:37   ` Johannes Schindelin
2007-11-08  0:41   ` [PATCH v2] " Johannes Schindelin
2007-11-08 14:54     ` [PATCH] Remove deprecated commands from command list and update manpages Jonas Fonseca
2007-11-08 15:00       ` Andreas Ericsson
2007-11-08 16:01         ` [PATCH] Drop deprecated commands from git(7) and update deprecation notices Jonas Fonseca
2007-11-08 21:01           ` Junio C Hamano
2007-11-09  0:20             ` [PATCH] Remove non-existing commands from git(7) and delete their manpages Jonas Fonseca
2007-11-09  1:21               ` [PATCH 1/3] Documentation: lost-found is now deprecated Junio C Hamano
2007-11-09  1:27                 ` Jonas Fonseca
2007-11-09  1:34                   ` Junio C Hamano
2007-11-09  1:22               ` [PATCH 3/3] Documentation: remove documentation for removed tools Junio C Hamano
2007-11-12  0:24                 ` [PATCH] Documentation: Fix references to deprecated commands Jonas Fonseca
2007-11-12  0:32                   ` Jonas Fonseca
2007-11-12  8:22                     ` Junio C Hamano
2007-11-12  9:37                       ` Jonas Fonseca [this message]
2007-11-19  1:54                     ` J. Bruce Fields
2007-11-19  7:44                       ` Jonas Fonseca
2007-11-09  2:38               ` [PATCH 2/3] Make check-docs target detect removed commands Junio C Hamano
2007-11-08 15:18       ` [PATCH] Remove deprecated commands from command list and update manpages Johannes Schindelin
2007-11-08 15:19         ` Johannes Schindelin

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=20071112093719.GA22555@diku.dk \
    --to=fonseca@diku.dk \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).