Git development
 help / color / mirror / Atom feed
From: "Nikola Knežević" <laladelausanne@gmail.com>
To: git@vger.kernel.org
Subject: format-patch problem when using relative
Date: Wed, 26 Nov 2008 17:12:02 +0100	[thread overview]
Message-ID: <17081052-4480-4971-9F38-BD5C48087379@gmail.com> (raw)

Hi,

I have a subdirectory in my top-level directory, which I merged using  
subtree strategy. I want to send my patches upstream, so I did  
something like:
git format-patch -o patches -n --relative=click click/master myclick

This produced a bunch of files in patches directory, most of which are  
empty. When I tried this --stdout, I had something like this:
[PATCH 8725/8846]
[PATCH 8726/8846]
[PATCH 8750/8846]
..
[PATCH 8845/8846]

So, it seems that format-patch was counting all patches, but only  
printing the interesting ones.

I'm running git 1.6.0.1 on FreeBSD7/amd64.

PS. Please CC me, since I'm not on the list.

Cheers,
Nikola

             reply	other threads:[~2008-11-26 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 16:12 Nikola Knežević [this message]
2008-11-26 18:01 ` format-patch problem when using relative Jeff King
2008-11-26 18:58   ` Nikola Knežević
2008-11-27  9:42     ` Björn Steinbrink

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=17081052-4480-4971-9F38-BD5C48087379@gmail.com \
    --to=laladelausanne@gmail.com \
    --cc=git@vger.kernel.org \
    /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