git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Patch-level-format conversion
Date: Thu, 16 Jun 2011 00:28:14 +0200	[thread overview]
Message-ID: <BANLkTi=w1SP6zEZGs1WQ_2L0bWQ2cneNSQ@mail.gmail.com> (raw)
In-Reply-To: <7v39jakajn.fsf@alter.siamese.dyndns.org>

Hi Junio,

On Thu, Jun 16, 2011 at 12:13 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Sedat Dilek <sedat.dilek@googlemail.com> writes:
>
>> I played a bit with git format-patch and git diff and got some helpful
>> hints from friends of #grml and #quassel.de.
>> Attached is the README.txt I produced some hours ago.
>>
>> Regards,
>> - Sedat -
>>
>> Q: How to generate freetz-conform patches out of a GIT repository?
>>
>> A. Follow these instructions.
>>
>> ### Checkout freetz development branch
>> svn co http://svn.freetz.org/trunk/ freetz-trunk
>> cd freetz-trunk/
>>
>> ### Get latest revision
>> revision=$(LC_ALL=C svn info | grep "Last Changed Rev" | awk {'print $4'})
>> echo $revision
>>
>> ### Turn freetz-trunk source-dir into a GIT repository
>> git add --ignore-errors ./ ; git commit -m "`basename $PWD` SVN revision $revision"
>
> Wouldn't "add ./" add all the cruft in .svn (and its huge "pristine"
> subdirectory)?  Why --ignore-errors?
>

I used to use it after reading the blog-post in [1].

>> ### Edit some files and save changes
>> $EDITOR file1 file2
>>
>> ### Extract patchset
>> git format-patch --no-prefix --no-numbered $FIRST..$LAST
>
> You would need to record your own changes made by the $EDITOR step in
> commits before asking format-patch to make patch files out of them, but I
> do not see that step.
>

Ooops, yeah missed the git commit command(s) :-(.
Thanks for the pointer!

> Also it is unclear how you determine $FIRST and $LAST.  FIRST must name
> the commit that is the _parent_ of your first commit (i.e. your sample
> command line tells $FIRST to be excluded).
>

It's just an example...
IIRC I really did "git format-patch --no-prefix -19" (extract last 19 commits).
Hmmm, remember I got no "origine" for initial commit...

>> ### Some git format-patch options explained:
>>       --no-prefix: Do not show any source or destination prefix.
>>    -n, --numbered: Name output in [PATCH n/m] format, even with a single patch.
>> -N, --no-numbered: Name output in [PATCH] format.
>>
>>
>> - Sedat Dilek <sedat.dilek@gmail.com> (15-Jun-2011)
>

- Sedat -

[1] http://who-t.blogspot.com/2009/06/git-patches-from-tarballs.html

      reply	other threads:[~2011-06-15 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimRArtFBqA4BFASjkS9BC1sbSfUJQ@mail.gmail.com>
2011-06-15 20:55 ` Patch-level-format conversion Jonathan Nieder
2011-06-15 21:16   ` Sedat Dilek
2011-06-15 22:13     ` Junio C Hamano
2011-06-15 22:28       ` Sedat Dilek [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

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

  git send-email \
    --in-reply-to='BANLkTi=w1SP6zEZGs1WQ_2L0bWQ2cneNSQ@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=sedat.dilek@gmail.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).